get_membership

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

With no annotations, the description carries full burden. It states 'compact' but does not explain what that implies (e.g., limited fields, summary format). No information on idempotency, authentication, rate limits, or side effects is given. Behavioral transparency is minimal.

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 sentence of seven words, making it concise. However, it is too terse and lacks necessary details that could be added without becoming verbose. It achieves conciseness but at the cost of informativeness.

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 the presence of an output schema, the description does not need to detail return values, but it fails to explain 'compact' or any constraints. The tool is simple (one required param), but the description leaves significant gaps in understanding the tool's exact behavior and output.

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%. The description adds no meaning beyond the schema: it says 'by id' but does not clarify what the membership_id represents (e.g., a record ID, user ID, project membership ID). The parameter remains under-documented.

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 it retrieves a membership summary by ID. The verb 'Get' and resource 'membership summary' are specific. However, it does not explicitly distinguish from sibling tools like list_project_memberships or get_project, though the purpose is clear enough for a single-entity retrieval.

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?

No usage guidance is provided. There is no mention of when to use this tool versus alternatives such as list_project_memberships or get_user. The agent receives no context on prerequisites or appropriate scenarios.

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