Get Organization Membership

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds only the required scope 'organizations:read', which is real auth context beyond the annotations, but it says nothing about what a 404/permission failure looks like or what data is returned.

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?

Three short, front-loaded fragments with no padding. 'Reads Calendly data' is mild boilerplate that could be dropped, but nothing else is wasted.

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 simple single-resource getter with a fully documented two-parameter schema and complete safety annotations, the essentials are present. However, with no output schema the description does not hint at the response shape or error behavior, leaving a small but real gap.

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 schema already explains that 'account' selects credentials rather than an organization URI and that membership_uuid is the membership identifier. The description adds no meaning beyond that, so the baseline 3 applies.

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 first sentence restates the title and name almost verbatim, which is close to tautology, but 'Reads Calendly data' confirms this is a read-only retrieval. It does not distinguish this single-item getter from the sibling list_organization_memberships, so an agent gets only the minimal viable signal.

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?

There is no statement of when to use this tool versus alternatives such as list_organization_memberships or get_organization. Nothing indicates that a membership_uuid is prerequisite data the agent must already possess.

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