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

Annotations provide readOnlyHint=false (consistent with removal) and destructiveHint=false (possibly implying reversibility). The description mentions a grace-period warning and resubscribe link, suggesting potential reversibility or consequences. However, it does not fully disclose what happens to the learner's data or whether the action can be undone. Still adds meaningful context beyond annotations.

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 a single paragraph with multiple sentences, each adding necessary information. It is front-loaded with the main action. Could be slightly more concise (e.g., merging some sentences), but the length is justified by the amount of critical usage guidelines.

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 no output schema and limited annotations, the description covers tool purpose, prerequisites, permission checks, business restrictions, and a required parameter value. It lacks detail on return values or the exact effect on the learner, but these may not be essential for selection. Overall, it provides sufficient context for an agent to decide to use this tool.

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% (no parameter descriptions). The description only explains the 'confirm' parameter must be 'REMOVE_MEMBER'. It does not elaborate on 'learnerId', 'communityId', or 'removalReason', which leaves ambiguity. Parameter names are somewhat self-explanatory, but more specifics would help.

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 clearly states 'Remove a learner from a managed community,' specifying the verb and resource. It distinguishes from siblings like 'remove_community_member' by noting that 'business and community refer to the same thing and are interchangeable,' though it could be clearer why both tools exist. The phrase 'managed community' adds specificity.

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 instructions: requires 'confirm' set to 'REMOVE_MEMBER', check business permissions, FREE businesses cannot use, call check_business_tool_access first, and show grace-period warnings. It tells when not to proceed (access blocked). This is comprehensive guidance for an AI agent.

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