QueryDocumentFull

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states 'Retrieve' but says nothing about authentication requirements, read-only semantics, output shape, error behavior, or data size expectations. It is not misleading, but it is also not informative.

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 phrase with no redundant information. It earns a 4 because it is concise, though slightly under-specified.

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, no annotations, and several closely related sibling tools, so the description needs to clarify what result the agent can expect and how this query differs. It covers only the basic retrieval intent and leaves those important details unstated.

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 and has no parameters, so the baseline of 4 applies. The description does not add parameter semantics, but none are needed for this tool.

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 clear verb ('Retrieve') and a resource ('Document and Scan Data'), so the core operation is understandable. However, it does not explain how QueryDocumentFull differs from the sibling QueryDocument or what 'Full' adds, leaving some ambiguity.

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 about when to use this tool versus QueryDocument, QueryDocumentChecks, VerifyDocument, or RetrieveResult. The tool name implies a broader scope, but the description itself provides no when-to-use or when-not-to-use context.

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