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

Annotations already declare destructiveHint=true and give the title, so the write/mutation nature is covered. The description adds the underlying API call ('POST /members'), which is mildly useful context for an agent working against the Current RMS API. It does not disclose auth requirements, side effects on linked records, or rate limits, so it adds little beyond the annotation.

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 sentences, front-loaded with the core action and followed by the one non-obvious linking rule and the endpoint reference. No filler, no repetition of schema content.

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 10-parameter creation tool with nested objects and no output schema, the description covers the essentials (entity types, the linking case) but omits what the call returns — notably whether the new member's id comes back — and says nothing about required fields or the destructive/creation side effects. Adequate but with real gaps for a mutation tool.

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%, so every one of the 10 parameters is already documented in the schema, and the description's parent_member_id note largely restates the schema text. Baseline 3 applies; the description adds no new format, constraint, or default information beyond what the schema provides.

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?

States a specific verb and resource ('Create an Organisation, Contact or Venue') and names the membership_type values, so the agent knows exactly what entity is produced. It is clearly distinguishable from create_activity and create_opportunity by resource. It stops short of explicitly contrasting with update_member or list_members, but the purpose is unambiguous.

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?

It provides one useful usage instruction — pass parent_member_id to link a new Contact to its Organisation — which is genuine when/how guidance. However there is no guidance on when to use this vs. update_member, no mention of prerequisites or permissions, and no exclusions. Usage is implied rather than framed.

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