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

The description describes a destructive action (removing an admin with a DELETE confirm parameter) but annotations set destructiveHint to false. This is a clear contradiction. Additionally, no other behavioral details like cascading effects or required permissions are provided.

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 dense but not overly verbose. Each sentence adds important context, though the structure could be improved with clearer separation of prerequisites vs. behavior. It remains efficient overall.

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 simple action and no output schema, the description covers preconditions and a key parameter. However, it lacks details on return values, error handling, and the exact impact on the admin (e.g., notification, permissions). The contradiction with annotations also undermines completeness.

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?

The description clarifies that the confirm parameter must be set to 'DELETE', adding meaning beyond the schema which only defines type. However, no explanation is given for email or communityId, and schema coverage is 0%. The description partially compensates for one parameter.

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 states 'Remove an admin from a community' and equates business with community, but fails to distinguish this tool from the sibling 'remove_community_admin', which likely serves a similar purpose. This lack of differentiation creates confusion.

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 description provides explicit prerequisites: confirm must be 'DELETE', check business permissions, call check_business_tool_access before inputs, and never proceed when access is blocked. It also notes FREE businesses cannot use the tool. However, no guidance is given on when to use this versus remove_community_admin.

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