get_membership

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

No annotations exist, so the description is the only safety signal; 'Get' implies a read-only operation and 'compact summary' hints at the response shape. It does not disclose permissions, error behavior, or handling of unknown ids, but for a simple getter this is minimally acceptable.

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?

One short sentence with no redundant words; 'Get a compact membership summary by id' is front-loaded and immediately usable.

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 one required parameter and the presence of an output schema, the description is nearly sufficient for a basic get-by-id call. It would be more complete with an explicit pointer to list_project_memberships for discovering ids or a note on membership scope.

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%, but the description's 'by id' does tell the agent that membership_id is the lookup key. It adds no detail on the integer format, source, or validation, so it only partially compensates for the missing schema documentation.

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 uses the specific verb 'Get,' names the resource 'compact membership summary,' and qualifies it by 'id.' This clearly marks it as a single-record fetch and distinguishes it from the plural list_project_memberships sibling.

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 explicit when-to-use or alternative guidance. 'by id' implies usage when the caller has a membership id, but list_project_memberships is never mentioned, so the tool cannot be selected against alternatives with full confidence.

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