get_membership

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

There are no annotations, so the description carries the full behavioral burden. 'Get details' signals a read operation, but the description discloses nothing beyond that: no response shape, error behavior, permissions, or entity relationship. This is minimal and adds little beyond restating the tool's action.

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 a single, front-loaded sentence with no filler. Every word contributes to identifying the operation and resource, making it easy for an agent to parse quickly.

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 one-parameter get-by-ID tool, the description is minimally adequate. However, there is no output schema and no annotations, so the description should clarify what 'account membership' refers to and what details are returned. The potential confusion with sibling tools like list_account_members is not addressed.

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 100%, and the only parameter membership_id is documented as 'The membership ID.' The description does not add extra meaning to the parameter, but because the schema already fully explains it, a baseline score of 3 is appropriate.

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 clear verb and resource: 'Get details of a specific account membership.' It is easy to understand what the tool does, and the required membership_id confirms a get-by-id operation. However, it does not explicitly differentiate itself from siblings such as list_memberships or get_account, so it stops short of full differentiation.

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 provides no explicit guidance about when to use this tool versus alternatives like list_memberships or list_account_members. The word 'specific' weakly implies a get-by-ID use case, but there are no stated conditions, exclusions, or references to sibling tools.

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