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

Annotations are readOnlyHint=true, so agent knows no destructive action. Description adds context: legacy route, FREE business restriction, mandatory pre-checks with warnings. Adds value 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?

Description is verbose and front-loaded with unclear phrase ('legacy manager memberships-for-admin route'). Contains procedural steps that could be more concise. Lacks clear structure.

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?

No output schema and description fails to mention return value, pagination, or filtering. Missing parameter explanation. Incomplete for a list 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 0% and description gives no explanation for communityId parameter. Agent cannot infer its meaning or usage from description alone.

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 says 'Call the legacy manager memberships-for-admin route' without stating the actual purpose of listing members. Title implies it lists members, but description doesn't confirm. Vague purpose.

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 prerequisites: check business permissions, FREE businesses cannot use, call check_business_tool_access, show warnings. But no guidance on when to use this vs sibling tools like list_community_members_with_filters.

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