QueryDocument

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Retrieve Document Details' and does not clarify whether this is read-only, what data is returned, whether it requires IDs, or how it differs from QueryDocumentFull and QueryDocumentChecks.

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 extremely short and front-loaded, which is concise. However, it is closer to under-specification than to efficient completeness, because it omits almost all decision-relevant information.

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 large sibling set of document tools with overlapping names, this description is insufficiently complete. It does not state return behavior, input expectations, or how this tool relates to QueryDocumentFull, QueryDocumentChecks, or VerifyDocument, so an agent cannot confidently select 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 input schema is empty with zero parameters and 100% schema description coverage, so there are no parameter semantics to explain. Per the rubric, zero parameters receives a baseline score of 4.

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 a specific verb and resource: "Retrieve Document Details," making the core action clear. However, it does not differentiate itself from sibling tools like QueryDocumentFull or QueryDocumentChecks, so the purpose is clear only at a basic level.

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 versus alternatives. The description provides no context, conditions, or exclusions, leaving an agent to infer usage entirely from the tool name.

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