Get Membership

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

No annotations are provided, so the description carries the behavioral disclosure burden. The verb 'Get' and word 'single' reasonably signal a read-only retrieval of one membership, but not-found behavior, permissions, and side effects are not addressed. Adequate for a simple fetch, but shallow.

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. It communicates action, resource, cardinality, and selection criterion efficiently.

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?

With only one required parameter and an output schema available, the description is nearly complete for invoking the tool correctly. It lacks an explicit pointer to get_all_memberships for listing scenarios, but that is a minor gap at this complexity level.

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 0% description coverage, so the description must compensate. 'by ID' clearly maps the only required parameter, id, to the membership being retrieved. For a one-parameter tool this is sufficient, even though no format details are provided.

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?

Description uses a specific verb 'Get', identifies the resource 'membership', and narrows the scope with 'a single' and 'by ID'. This clearly distinguishes it from get_all_memberships and from update/delete_membership siblings.

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 phrase 'a single membership by ID' implies use when you have one specific membership ID, but the description never explicitly names get_all_memberships as the alternative for listing. Guidance is present but implicit rather than explicit.

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