update_membership

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

No annotations are provided, and the description only states what fields can be updated. It does not disclose potential side effects, authentication requirements, idempotency, or any impact on other entities. As a mutation tool, it should explain that it modifies the membership record.

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 very concise: two short sentences plus example queries. The purpose is front-loaded in the first sentence, and the examples are immediately useful. Every part adds value without redundancy.

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 has 4 parameters including a required membership_id and no annotations, the description is incomplete. It lacks parameter constraints, behavioral notes, and any details about the output (though output schema exists). The minimal information may lead to incorrect usage.

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 description coverage is 0%, so the description must compensate. It mentions three of the four parameters (tier, end_date, status) but does not specify formats, allowed values, or constraints for any parameter, including the required membership_id. This leaves significant ambiguity.

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 it updates a membership, listing specific fields (tier, end date, status). It distinguishes from siblings like create_membership and cancel_membership. However, it does not explicitly state that it modifies an existing membership, though it is implied by the examples.

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 example queries (e.g., 'extend membership 67890 to year-end') that effectively illustrate when to use the tool. It does not include when-not-to-use or alternatives, but the examples are sufficiently clear for typical scenarios.

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