DataKiosk_getDocument

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

With no annotations, the description carries the full burden of explaining behavior. It does disclose that the tool returns retrieval information rather than the document contents themselves, which is useful, but it does not explain the nature of that information, the return format, side effects, or any authorization requirements.

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 and mostly readable, but 'Catalog entry.' is an unexplained meta-label that does not earn its place, and the deployment note is placed before the actual purpose. It is concise but not optimally structured.

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 is no output schema and no annotation coverage, so the description must be self-sufficient. It fails to explain what 'the information required for retrieving a Data Kiosk document's contents' actually is, leaving an agent unsure what the return value will contain or how to use it.

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 tool has zero parameters and the schema coverage is 100%, so there is no parameter semantics to document. The empty schema with additionalProperties true is slightly risky, but the description has no obligation to explain non-existent inputs.

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 clear objective: it returns the information needed to retrieve a Data Kiosk document's contents, which distinguishes it from the sibling query-focused DataKiosk operations. However, the opening 'Catalog entry' and 'Runs in your Kuudo deployment, not here' add ambiguity about whether this tool is actually invocable or merely descriptive.

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?

No when-to-use or when-not-to-use guidance is given. It does not mention alternatives like DataKiosk_getQuery, and the 'Runs in your Kuudo deployment, not here' note is a deployment caveat rather than a usage criterion.

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