update_membership_status

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

With no annotations provided, the description must disclose behavioral aspects on its own. It only states the action (update AASM status) with examples, but does not mention required permissions, side effects, valid state transitions, or reversibility. This is a significant gap for a mutation tool.

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 only two sentences long, front-loads the action, and the differentiation is packed into the second sentence without any unnecessary words. Every sentence earns its place.

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?

The description covers the core function and differentiates from the sibling, but because there are no annotations and no output schema, it lacks information about response format, error conditions, or required permissions. For a mutation tool, this is a notable gap, making the description merely adequate.

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 already covers both parameters at 100%, but the description adds value by giving concrete examples of valid statuses ('activate, suspend'), which clarifies the otherwise vague 'Target AASM state' schema text. This goes beyond the structured data.

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 verb 'Update', the resource 'membership', and the specific scope 'AASM status'. It explicitly contrasts with `update_membership`, which patches role_level/preferences, making the purpose unambiguous and differentiated from sibling tools.

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 directly names the alternative tool (`update_membership`) and clarifies what it does instead, providing explicit when-to-use and when-not-to-use guidance. This is exactly what the dimension asks for.

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