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

Annotations are limited (destructiveHint: false) but description adds important behavior: requires confirm=DELETE and interchangeability note. Does not contradict annotations and provides context beyond structured fields.

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?

Five sentences in a single paragraph. Front-loads action but includes lengthy instructions. Could be more concise and structured (e.g., bullet points). However, all sentences are relevant.

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 tool with no output schema and 3 parameters, description covers the critical confirm requirement and preconditions. Lacks return value info and email parameter details, but overall sufficient for agent to use safely.

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 has 0% description coverage. Description adds critical constraint on confirm parameter ('requires confirm set to DELETE') which is not in schema. Does not explain email or communityId beyond schema, but the added value is significant.

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?

Description clearly states 'Remove an admin from a community', specifying verb and resource. Also clarifies that 'Business and community refer to the same thing', but this may cause confusion with the sibling tool 'remove_business_admin' which exists separately.

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?

Provides explicit instructions: check business permissions, FREE businesses cannot use, call check_business_tool_access first, and handle grace-period warnings. Clearly guides when to use and when not to proceed.

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