get_membership

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

No annotations are provided, so the description must carry the full burden. It indicates a read operation fetching membership details but does not disclose error behavior (e.g., 404 for missing id) or any permissions needed. However, given the tool's simplicity, the description is adequate.

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 two sentences: the first states purpose and content, the second gives a usage example. It is front-loaded and contains no fluff, earning a high score.

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 tool has an output schema (not shown) which likely documents return values. The description covers purpose, content, and usage. For a simple single-parameter fetch, this is nearly complete, only missing potential details like error states.

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 parameter (membership_id) with no description. Schema coverage is 0%, but the description implies the parameter by saying 'by id'. For a single obvious parameter, this is acceptable, though explicit mention would improve clarity.

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 'Fetch a single membership by id' and specifies the returned fields (tier, status, dates, billing). It distinguishes from siblings like list_memberships (list) and update_membership (modify).

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 includes a concrete usage example 'show membership 67890's full details', providing clear guidance on when to use the tool. While not explicitly stating when not to use, the example suffices for a simple fetch operation.

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