get-item

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

Discloses resolution by id, exact name, or case-insensitive name, and the special behavior for unidentified items (trueName). No annotations exist, so description carries burden well.

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?

Three sentences, no filler. Front-loaded with core purpose, then resolution methods, then edge case. Every sentence adds value.

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?

Describes returned data comprehensively (system data, effects, flags, description) and covers the unidentified item case. No output schema, so description fills the 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?

Adds case-insensitivity and reliability details to the schema's identifier description. With 100% schema coverage, this provides meaningful extra context.

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 it retrieves a single world-level Item document with full data, distinguishing it from sibling list-items. The verb 'Retrieve' and resource 'Item' are specific.

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?

Explicitly advises using list-items first to find ids, providing clear context. Does not cover when not to use or all alternatives, but sufficient for a retrieval tool.

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