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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral rule not present in the annotations: the specId-wins precedence when both identifiers are supplied. No return format or result-limit behavior is described.

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 dense sentence that front-loads the retrieval modes, then the precedence rule, then the list filter. No filler, and the most important disambiguation comes first.

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 read-only, three-parameter tool with full schema coverage and annotations, the description covers modes, precedence, and filtering adequately. Since there is no output schema, a brief note on what a spec record or list contains would be the only remaining gap.

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 100%, so every parameter is already documented, and the description's status default and identifier behavior largely restate the schema. The only added semantics is the conflict resolution between specId and sourceUrl, which is marginal over the schema baseline.

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?

States a specific verb (retrieve) and resource (stored spec) and explicitly enumerates both operating modes: fetch by ID, fetch by source URL, or list. This distinguishes it cleanly from write-oriented siblings like save_spec and update_spec.

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?

Gives clear selection rules: omit both identifiers to list, and specId takes precedence when both are supplied. It also notes the list-mode status filter and its default. It does not point to sibling tools for adjacent operations, but the when-to-use guidance for this tool's own modes is complete.

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