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

No annotations are provided, so the description must carry the full burden. It only says 'with full metadata'—a vague term—and does not disclose auth requirements, rate limits, error cases, or what exactly 'full metadata' includes. The read-only nature is implied by 'fetch' but not explicitly stated.

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?

Two short sentences with no filler. The first sentence states the action, the second provides a crucial alternative. Every word earns its place.

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?

For a simple get-by-id tool, the description covers the essential purpose and the main alternative. However, without an output schema, the phrase 'full metadata' is vague and could leave the agent uncertain about the return structure. Still, the tool is simple and the description is largely complete.

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 only parameter is 'id', and the description clarifies it refers to the track id via 'by id.' However, with 0% schema coverage, the description adds no extra detail about the parameter (e.g., format, constraints), though the schema already provides format and pattern. It is adequate but not compensating beyond the obvious.

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?

'Fetch one learning track by id with full metadata' uses a specific verb and resource, clearly distinguishing it from related tools. The reference to 'ordered curriculum' differentiates it from hivelearn_list_track_courses.

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 explicitly states when to use this tool (to fetch a single track's metadata) and provides a direct alternative: 'For its ordered curriculum use hivelearn_list_track_courses.' This is clear and actionable.

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