get_item

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

With no annotations, the description must carry the behavioral transparency burden, but it only says 'Get details'. It does not disclose expected response shape, error behavior (e.g., not found), authentication needs, or side effects, though 'Get' does imply a read-only 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 very short and front-loaded, with no fluff. However, it is under-specified and contains a grammatical error ('a item'), so it is not a well-crafted concise description that earns its place through substance.

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 the two required parameters, no output schema, and no annotations, the description is too minimal to be complete. It does not mention why campaignId is needed, what 'details' includes, or any behavior around missing or invalid identifiers, so an agent cannot reliably invoke it with full confidence.

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% and the description adds no meaning to the parameters. The required campaignId and id are both undocumented, and the description does not explain their relationship or how they should be used to fetch the item.

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 states a clear verb ('Get') and resource ('item'), so an agent can infer this is a read operation for a single item. It is not a tautology and is distinguishable from siblings like list_items and get_character by naming the item resource. However, it does not explicitly differentiate itself from similar get_* tools or clarify scope beyond 'details'.

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 no guidance on when to use this tool versus list_items, search, or other retrieval tools. There is no mention of prerequisites, campaign context, or exclusions, leaving the agent to guess when get_item is appropriate.

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