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

Annotations already declare openWorldHint=false, destructiveHint=false, and (notably) readOnlyHint=false, so the safety profile is covered by structured fields. The description adds no behavioral context at all — no note on whether the flag-disabled readOnlyHint has practical consequences, no permission or scope information — so it earns little credit here.

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?

One sentence, front-loaded with the usage trigger and containing no redundant or filler content. Every clause 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 single-parameter read tool with a full input schema and an output schema that documents the return shape, the description covers everything an agent needs to call it. The only missing piece is explicit differentiation from search_assignments.

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 schema coverage at 100% and a single fully documented 'id' parameter (pattern and length constraints included), the schema carries the parameter semantics. The description only restates that an assignment ID is required, adding nothing beyond the schema, so the baseline of 3 applies.

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 names the resource (assignment) and the operation (returning its full details by ID), which is a clear verb+resource pair. It does not, however, distinguish itself from the sibling search_assignments, leaving the agent to infer the difference between a lookup-by-ID and a search.

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?

It gives a concrete trigger condition: the user supplies an assignment ID and wants the complete record. This implicitly routes away from search_assignments, but no alternative or exclusion is named explicitly, so it stops short of full when/when-not guidance.

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