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

No annotations are provided, and the description does not disclose side effects, auth needs, rate limits, or output structure. It implies a read-only retrieval but does not confirm safety or performance traits.

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 sentence, which is concise but omits crucial details. It front-loads the action but lacks structure to highlight key aspects like parameter usage or result format.

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?

With 5 parameters, no output schema, and no annotations, the description is grossly inadequate. It fails to explain what the tool returns, how to use parameters effectively, or any constraints/edge cases.

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 only mentions 'documents' and 'collection_id', ignoring 'query', 'top_k', and 'rerank'. Without explanation, the agent cannot understand parameter roles or defaults, especially for required 'query'.

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 clearly states it runs a 'simple product retrieval helper' using documents or a collection ID. It specifies the action and input resources, distinguishing it from siblings like query_data which may be more general. However, the term 'simple' and 'helper' are slightly vague.

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 guidance on when to use this tool vs. alternatives. It mentions two input modes but does not explain when to use each or provide exclusion criteria. The description lacks decision cues.

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