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

The annotations already declare destructiveHint=true, and the description is consistent by opening with 'MUTATES' and specifying the metadata-only scope. It adds useful constraints on metadata size, though it does not discuss permissions, reversibility, or rate limits.

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 short and front-loaded: it leads with the mutation warning, then constraints, then the alternative tool, then the underlying GraphQL call. There is little wasted text.

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 simple two-parameter mutation with rich schema coverage and a destructive annotation, the description gives enough context to invoke it correctly and avoid using it for unsupported fields. It does not explain return values, but the tool is otherwise adequately covered.

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 100%, so the schema already documents both id and metadata. The description repeats the metadata constraints and names the underlying GraphQL mutation, but adds little parameter meaning beyond what the schema provides.

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 states a specific verb and resource: it MUTATES Memberful data by updating a member's metadata. It also distinguishes this tool from memberful_graphql by clarifying that only metadata updates are supported here, while other inline member fields belong in the GraphQL tool.

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?

It explicitly says to use this tool only for member metadata updates and directs the agent to memberful_graphql for other inline member fields. That gives a clear when-to-use and alternative-routing rule.

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