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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool stops generation, implying a state change but not destructive. It mentions permission checks and free business restrictions. While it doesn't describe side effects (e.g., whether other generations are affected), the annotations cover the safety profile. The description adds useful 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 short paragraph with no wasted words. It front-loads the action, then provides sequential instructions. Every sentence adds value: initial purpose, permission check instruction, free business restriction, prerequisite call, and warning handling. It is efficient and well-structured.

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 tool simplicity (one parameter, no output schema, annotations present), the description covers key aspects: what it does, prerequisites, exclusions, and required prior actions. However, it does not describe the tool's return value or confirm what happens upon success (e.g., confirmation message). Still, for a straightforward stop action, the completeness is high.

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 input schema has one parameter (communityId) with 0% description coverage. The description mentions 'for a community' but does not explain the parameter's format, source, or constraints beyond what the schema provides (minLength: 1). Given the low coverage, the description fails to compensate with additional parameter meaning. The parameter name is somewhat self-explanatory, but the description adds little value.

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 the action ('stop') and the resource ('Get Inspired AI template generation' for a community). It distinguishes from sibling tools like get_get_inspired_page (read) and check_business_tool_access (permission check). The verb and object are specific and unambiguous.

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: check business permissions, call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, and never proceed when access is blocked. It also notes that FREE businesses cannot use this tool, giving clear when-not-to-use guidance. This fully informs the agent about prerequisites and alternatives.

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