snipe_item

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool returns a 'full record' with evidence, candidates, factors, and notes, which implies a read-only retrieval operation, but it does not state permissions, side effects, or other operational constraints.

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 free of filler, with the returned content front-loaded after a colon. However, it is a sentence fragment rather than a complete, structured tool description, leaving key elements such as the action and parameter semantics unstated.

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?

An output schema exists, so return values need not be fully explained, but the description remains incomplete for an agent to invoke the tool correctly. With no annotations, 0% schema description coverage, and many sibling tools, it omits parameter guidance and selection context.

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 'id' parameter, and the description does not explain the parameter's format or meaning. The phrase 'one issue/opportunity' loosely implies the id identifies the entity, but the description adds almost no semantic detail beyond the bare schema.

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 identifies the resource ('one issue/opportunity') and some returned fields, but uses a noun phrase with no explicit action verb. It does not distinguish itself from siblings like get_snipe_context, snipe_list, or next_snipe.

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 when-to-use guidance, no prerequisites, and no alternatives named. The closest thing to usage context is the implied retrieval of a single issue/opportunity, which is not enough to tell an agent when this tool should be selected over related snipe tools.

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