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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description still adds real value by disclosing that password hashes and payment-provider data are excluded from the response, a data-exposure fact the annotations cannot express.

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 compact fragments: the highest-value content (what is returned) comes first, the exclusion note second, the endpoint last. Every clause carries information; there is no filler.

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 single-entity read with no output schema, enumerating the returned fields substitutes well for a return-value spec, and the exclusion clause covers the obvious privacy question. What is missing is any statement of error behavior for a bad or unknown member_id.

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% and the single parameter is fully documented (24-hex pattern plus a pointer to hello_club_list_members for discovery). The description adds nothing about member_id beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb and resource ('One member by id') and then enumerates the exact payload returned: profile, contact details, roles, subscriptions, credit, amount owing, custom fields. That enumeration makes it unmistakably distinct from hello_club_list_members and the other get_* siblings.

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?

Usage is only implied: 'one member by id' signals fetch-single, and the endpoint string GET /member/{id} confirms it. It never explicitly says when to use this instead of hello_club_list_members or what to do if the id is unknown (that routing hint lives only in the schema's parameter description, not the tool description).

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