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

With no annotations provided, the description carries the full burden of behavioral disclosure and provides none: no permission requirements, no statement of what is returned, no error behavior for unknown IDs. An agent learns nothing beyond the bare existence of the operation.

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 a single fragment with no waste, but it is under-specified rather than concise. Brevity here reflects missing information, not efficient communication.

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 lookup with no output schema and no annotations, the description should at minimum explain what metadata is returned and how item_id is formed. Neither is present, and '(any source)' leaves the resolution rules opaque.

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 0% for the single required item_id, and the description adds no format, type, or example for it. '(any source)' very slightly implies the ID is source-agnostic, but that is not enough to compensate for the coverage gap.

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 is a noun phrase with no verb, essentially restating the tool name 'get_item' as 'Item metadata'. The parenthetical '(any source)' hints at scope but does not clarify whether this returns a single item, its type, or which fields.

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?

There is no explicit when-to-use guidance, no prerequisite, and no named alternative such as list_items or a source-specific getter. '(any source)' only weakly implies this spans sources where other tools might not, leaving routing to inference.

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