DataKiosk_getQuery

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It does communicate that the operation returns query details and runs in the Kuundo deployment, but it does not explicitly state read-only/no-side-effect behavior, error cases, or authentication concerns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the key purpose is not front-loaded: 'Catalog entry' and the deployment note appear before the actual function. The 'Catalog entry' fragment is unclear and does not clearly earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There are no annotations, no output schema, and an empty input schema, so the description must cover more ground. It does not explain where queryId comes from, what the returned query details contain, or how this relates to the sibling DataKiosk operations, and 'Catalog entry... not here' leaves invocation context ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero properties, so the description's mention of 'the queryId parameter' is the only documentation of how to invoke the tool. It adds essential meaning but still omits type, format, and requiredness information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Returns query details') and identifies the resource by the queryId, clearly implying a single-query lookup rather than a list operation. The 'Catalog entry' sentence adds noise, and there is no explicit comparison to siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool over DataKiosk_getQueries, DataKiosk_getDocument, or DataKiosk_createQuery. 'Runs in your Kuundo deployment, not here' is an environment note, not a selection rule; only a weak implication that queryId must already exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.