Get ONES Document Context

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

Annotations already indicate read-only, idempotent, and open-world behavior. The description adds no additional behavioral traits, such as how the automatic selection works, whether it uses AI or rules, or what happens if no relevant content is found. It provides minimal value beyond the annotations.

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?

A single sentence that is direct and to the point. No unnecessary words or redundancy. It is appropriately sized for the tool's complexity.

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 that the tool has annotations and an output schema (not shown), the description is adequate but lacks context on the selection logic and edge cases. It does not explain what 'auto' mode entails or how to interpret the output. More detail would improve usability for an AI agent.

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 description coverage is 0%, so the description should explain parameter meanings. However, it only mentions 'based on a question' without detailing parameters like ref, max_chars, include_resources, or the mode enum. The parameter names give some clues, but the description adds no explicit semantics beyond the schema.

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 the tool's function: automatically selecting sections or chunks for a ONES document based on a question. It specifies the resource (ONES doc) and the action (select sections/chunks), and distinguishes it from sibling tools like get_doc or get_doc_chunks by implying it performs smart selection rather than full retrieval.

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 versus alternatives. Sibling tools like get_doc, get_doc_chunks, and search_docs exist, but the description does not explain when to prefer get_doc_context. Missing information on prerequisites, context, or exclusions.

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