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

Annotations only provide destructiveHint=true; the description adds the underlying POST endpoint and the parent-child linking behavior, but omits permissions, duplicate handling, and what is returned or whether the call is idempotent. Because annotations are sparse, this is a moderate but incomplete disclosure.

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?

Two brief sentences plus the endpoint, front-loaded with the action and the special linkage case. No wasted words; it is appropriately sized for a create tool.

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 create tool with ten parameters, nested objects, and no output schema, the description is thin: it omits required-field guidance, error behavior, and any indication of the response. The schema covers parameter meaning, but an agent still lacks behavioral context for a mutation.

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 the schema already documents all ten parameters in detail. The description adds only a linking hint for parent_member_id, which is marginal beyond the schema's own description.

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 (Create) and resource (Organisation, Contact, Venue), and distinguishes the membership_type options. It is clearly the member-creation tool among siblings, though it does not explicitly name update_member as the alternative for edits.

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?

Explains the three creatable member kinds and gives a concrete linkage rule for parent_member_id when creating a Contact under an Organisation. It does not state when not to use it or point to update_member for modifying existing members.

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