get_membership

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While it states 'detailed information', it does not specify what information is included (e.g., plan, dates, status). It also fails to note that this is a read-only operation with no side effects. For a fetch tool, this is insufficient transparency.

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, complete sentence that conveys the core functionality without any fluff. It is perfectly sized for a simple retrieval operation.

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 lack of an output schema and no annotations, the description should provide more detail about what the returned 'detailed information' includes. Without this, an agent cannot anticipate the response structure, which is critical for a get operation. The description is too minimal for a tool with zero additional context.

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 input schema has 100% coverage for its single parameter 'membership_id', with a clear description. The tool description echoes the need for an ID but adds no additional semantic value beyond what the schema already provides. Baseline 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 clearly states the action ('Get detailed information') and the resource ('specific membership') with the identifier ('by its ID'). This immediately distinguishes it from sibling tools like 'list_memberships' (which returns multiple) and 'update_membership' (which modifies).

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 implies usage via a membership ID, which is sufficient for a straightforward get-by-ID operation. However, it provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or context that would help an agent decide.

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