Detalle de documento

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

The description discloses that signatures are returned conditionally based on user visibility, which is a behavioral trait. However, with no annotations provided, it fails to mention other important aspects like mutation safety, authentication requirements, or error handling (e.g., what happens if the document does not exist or the user lacks permission).

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 a single, front-loaded sentence that conveys purpose efficiently. It is concise but could incorporate additional useful detail without becoming verbose.

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?

Given the tool's low complexity, the description provides the core function and visibility condition. However, it omits the return value structure (e.g., whether it returns full document data or metadata) and error scenarios, which are gaps given the absence of an output schema and annotations.

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?

Schema coverage is 0% and the description adds no information about the sole parameter 'documentId'. It does not explain what a valid ID looks like or how to obtain it, leaving the agent with only the schema's constraint (minLength 1).

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 uses the specific verb 'Obtiene' (gets) and clearly identifies the resource as a document by ID, including the addition of signatures. This distinguishes it from sibling tools like kairo_list_documents (listing) and kairo_download_document (downloading).

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?

Usage is implied: use when you need a specific document by ID. However, there is no explicit guidance on when not to use it (e.g., when to prefer listing first) or mention of alternatives among the many document-related siblings.

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