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

Annotations already flag destructiveHint=true, but the description goes well beyond them: it names what is deleted (what the crew kept of the user's runs), how fast the effect is (crew stops seeing runs at once), the cascading case (last member deletes the crew), and the no-op guard on confirm. That is exactly the extra context a mutation tool needs.

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?

Consequences are front-loaded in the first two sentences with zero fluff. The trailing 'Args: confirm: True to leave' largely repeats the earlier 'Nothing happens unless confirm is true', so one small redundancy keeps it off a 5.

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 single-parameter destructive mutation with an output schema and destructiveHint annotation, the description covers effects, timing, cascade, and the confirm gate, which is enough to call it safely. It never explicitly says the deletion is irreversible, which is the one gap worth adding.

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%, so the description must carry the single parameter, and it does: confirm is described as the leave switch and its false/no-op behavior is spelled out, which implies the default false. It could have restated the default explicitly rather than leaving it to inference, keeping this from a 5.

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 and resource (leave the user's Daash crew) and immediately names the distinguishing effects: runs stop being shared and the last member deletes the crew. That separates it cleanly from join_crew, get_crew, and update_crew without opening a 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?

The context for calling it (a user wanting out of a crew) is unambiguous, and it warns that nothing happens unless confirm is true. It does not explicitly route to siblings such as join_crew or update_crew, nor state exclusions, so it falls short of a 5.

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