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

With no annotations, the description carries the full behavioral burden, and it discloses only billing/cost behavior ($49 base, scaling above 100 exposed operators). It omits whether the recall is reversible, required permissions, whether it is destructive or state-changing, and what happens to related records.

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?

A single compact sentence with the action verb front-loaded, so it is easy to scan. The parenthetical pricing detail is dense but not wasteful given it encodes cost behavior.

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 mutation-style, three-parameter tool with no annotations and no output schema, this one-line description leaves critical information entirely absent: parameter meaning, authorization, reversibility, and return behavior.

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 0% across three parameters (lot_id, reason, severity), and the description says nothing about any of them — no format for lot_id, no allowed severity values, no guidance for reason. The description fails to compensate for the total schema 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?

Contains a specific verb+resource ('Issue ... recall'), so the agent knows this creates a recall. However, 'signed severity-classed recall' is undefined jargon and there is no differentiation from siblings like attest_remedy or record_exposure, which are also action/recording tools.

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?

No when-to-use, prerequisites, or alternatives are stated. The only contextual clause ('scaled above 100 exposed operators') describes cost scaling, not when the agent should pick this tool over its siblings.

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