remove_product

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

The description only says 'Deactivate tracking,' which implies a state change but provides no details on permanence, reversibility, side effects, or required permissions. Without annotations, this is insufficient for a mutation tool.

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 concise sentence, but it under-specifies the tool's behavior and context. It earns its place but could be more informative while remaining concise.

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 tool has an output schema but no annotations, the description should cover return behavior, error conditions, or side effects. It does not, leaving the agent with minimal understanding of what happens after invocation.

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?

With 0% schema description coverage, the tool name and description are expected to clarify the parameter. The description only implies 'product_id' identifies the product to deactivate, but adds no constraints or format details.

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 the action ('Deactivate tracking') and the target resource ('a product'), making it distinct from sibling tools like 'add_product' or 'check_product' which have different verbs.

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 guidance is provided on when to use this tool versus alternatives (e.g., when to deactivate vs. add or check a product). The description lacks context on prerequisites or scenarios.

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