Get Collection (Outline)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint, covering the safety profile. The description adds behavioral context by noting that 'includeStructure=true adds its document tree', which is beyond what annotations provide. It does not contradict 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?

The description is a single sentence that is front-loaded with the action. Every word is necessary and no extraneous information is present. It is exceptionally concise.

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 (2 params, simple) and the presence of annotations, the description covers the core purpose and a key behavioral detail. It does not explain return values, but no output schema exists. The description is nearly complete for its context, though a brief note about the response format would improve 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?

With 0% schema description coverage, the description must compensate. It adds meaning to the 'includeStructure' parameter by explaining its effect. However, it does not describe the 'id' parameter or its format, leaving a gap. The description provides partial but insufficient semantics for both parameters.

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 'Fetch one collection', which specifies the verb and resource. It also distinguishes the tool from sibling 'outline_list_collections' by indicating it fetches a single collection. The mention of 'includeStructure' adds specificity about an optional feature.

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?

The description implicitly guides usage: use this tool to fetch a single collection by ID, vs 'outline_list_collections' for listing all. However, it does not explicitly state when to use this tool over alternatives or any prerequisites, which would strengthen the guidance.

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