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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context beyond them: the cascade (link and scores are also removed) and the authorization requirement (organizer key), both of which affect how an agent should invoke it.

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?

Very short and the purpose is front-loaded, which is good, but it is a run-on sentence with a missing break before 'Needs', making it feel like a tidied title rather than a crafted description.

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 destructive cascade-removal tool, the description does disclose the auth requirement and what else gets deleted, and annotations carry the destructive/idempotent hints. However, it never explains the 'id' parameter, and with no output schema the agent gets no sense of the response beyond annotations.

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 only 50% – 'slug' is documented with a pattern and example, but 'id' has no description anywhere. The description adds no parameter meaning at all, so it fails to compensate for the undocumented half of the inputs.

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?

States a specific verb ('remove') and resource ('a judge') plus the scope of the removal ('their link and their scores'), which distinguishes it cleanly from the sibling add_judge. An agent can identify this as the inverse of judge creation without opening the schema.

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?

It gives a prerequisite ('Needs the organizer key') but no when-to-use or when-not-to-use guidance against alternatives. Usage is implied by the verb rather than stated, so it clears the minimum bar but leaves routing to inference.

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