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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context by specifying that SPEC §6/Q4 is enforced, causing restricted status for non-public-domain items. This goes beyond the structured annotations and helps the agent anticipate a possible restricted response. No contradiction with 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?

The description is two sentences, front-loads the primary purpose, and adds only the critical licensing behavior in the second sentence. Every element earns its place with no redundancy.

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 one-parameter read-only lookup, the description is nearly complete. It explains the singular scope and the key restricted-status behavior. However, with no output schema, it does not describe the response shape, error behavior, or field details, which leaves a minor gap for the 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?

The schema only provides a string 'id' parameter with no description, and schema description coverage is 0%. The description compensates by identifying the parameter as 'item_id' and clarifying that it refers to a survey item, adding essential meaning beyond the bare schema. A concrete example or format hint is missing, so the score is not a 5.

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: lookup one survey item by item_id. It distinguishes itself from sibling search tools by emphasizing 'one' and by id, so an agent can tell this apart from items.search without needing additional context.

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 gives clear context for when to use the tool: when you need a single survey item and have an item_id. It does not explicitly name alternatives or exclusion conditions, but the singular lookup framing makes the intended use reasonably obvious relative to search siblings.

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