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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read operation. The description adds critical behavioral context: access restrictions for free businesses and required permission checks. No contradictions with 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 of 4 sentences, front-loaded with purpose and followed by necessary usage guidelines. It is concise without being overly terse, though it could benefit from slight restructuring for readability.

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?

There is no output schema, so the description should clarify what the tool returns (the 'state' of the Get Inspired page). It does not describe the return value structure or fields. For a read operation, the agent needs to know what to expect, making the description incomplete.

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 schema has one required parameter (communityId) with 0% description coverage, meaning the description does not explain the parameter's purpose or format. While the parameter name is somewhat self-explanatory, the description fails to add meaning beyond the schema, which is necessary given the low coverage.

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 tool retrieves the 'Get Inspired page state' for a managed community. The verb 'Get' and resource 'Get Inspired page' are specific, and the tool is distinguished from many other 'get' sibling tools by targeting this unique page.

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 guidance: check business permissions, note that free businesses cannot use it, call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, and never proceed when access is blocked. This covers when and how to use the tool, and what prerequisites to check.

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