get_item

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's 'Read-only' repeats structured data. However, it adds the behavioral nuance about retrieving the current 'version' and contrasts with potentially stale data from search_items, which is useful beyond 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?

Two sentences, front-loaded with the core action. 'Read-only' is a concise fragment, and the usage guidance is phrased efficiently without redundant words. Every sentence 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 one-parameter, read-only getter with annotations, the description covers purpose, usage context, and behavioral expectations. The absence of an output schema is acceptable given the simplicity, and the guidance about search_items fills the main contextual 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?

The schema has one parameter 'key' with no description (0% coverage). The description clarifies that the key is the identifier used to fetch a specific item, directly encoding the parameter's role. While it doesn't elaborate on key format, for a single simple string the added semantics are adequate.

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 'Fetch one item by key' with a specific verb and resource, and it distinguishes itself from siblings by highlighting its role in obtaining a fresh version before mutating calls. This is specific and unambiguous.

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 states when to use this tool (right before a mutating call when a fresh version is needed) and names an alternative (search_items) with a conditional that avoids redundancy. This is strong contextual guidance.

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