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

Discloses destructive nature and details code resolution behavior, adding significant context beyond the annotations' destructiveHint. No contradictions.

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?

Two sentences, no fluff. First sentence covers purpose and action, second covers requirements. Efficient and well-structured.

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?

Covers main behavior, parameters, and prerequisites. Lacks mention of return value or success indication, but for a delete operation this is tolerable given no output schema.

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 coverage, description fully explains the required parameters (event_id, profile_id) and the action enum (detach vs delete_codes with their effects), filling the gap left by the 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?

Clearly states it deletes a discount profile and resolves its codes, with specific behavior for 'detach' and 'delete_codes' actions. Distinct from sibling tools like create, update, or list promo profiles.

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?

Explicitly requires event_id, profile_id, and host role. Does not compare to alternatives like remove_codes_from_profile, but context is clear enough for use-case selection.

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