get-item

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

No annotations are provided, but the description makes it clear this is a read-only retrieval operation ('Retrieve a single...document'). It does not mention any side effects, modifications, or destructive actions, which is appropriate for a get tool. Could be 5 but lacks explicit statement like 'Read-only'.

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 sentences, each conveying essential information: first describes what the tool retrieves, second provides resolution methods and usage recommendation. No wasted words.

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?

Given one parameter, no output schema, and no annotations, the description provides all necessary context: the type of document, what data is returned, how to identify the item, and even a pointer to the companion tool. It is fully sufficient for correct invocation.

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 coverage is 100% with the 'identifier' parameter described. The description adds beyond schema by specifying resolution priority: id (most reliable), exact name, then case-insensitive name. This additional context improves agent understanding beyond the basic schema definition.

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?

Description clearly states verb 'Retrieve a single world-level Item document' and specifies what is returned: 'full system data, embedded effects, flags, and flattened description'. It also lists three resolution methods (id, exact name, case-insensitive name), distinguishing from sibling 'list-items' which only returns ids.

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?

Description explicitly advises 'Use list-items first to find ids' and notes that id is 'most reliable', providing clear guidance on when to use this tool vs alternatives and the preferred workflow.

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