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

Discloses key behaviors beyond annotations: immediate application of split terms, no confirmation step, and refusal over existing terms unless replace_existing is true. Annotations are all false, so the description fully covers the behavioral profile.

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 sentences front-load the main action, then detail the split terms effect and refusal logic, and end with required IDs. No redundant information.

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?

Covers action, side effects (split terms), conditions (refusal/replace), and required inputs. Lacks mention of return value or confirmation, but no output schema exists. For a mutation tool, this is adequate.

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?

With 0% schema description coverage, the description adds meaning by naming required parameters and explaining the effect of replace_existing. It compensates for the silent schema, though it doesn't describe each parameter's type or constraints beyond names.

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 'Add a community member to a partner profile' with a specific verb and resource, and adds unique behavior (split terms apply immediately, refusal logic). This distinguishes it from sibling tools like add_guest, add_affiliate, and add_role.

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?

Provides explicit required parameters (community_id, profile_id, member_uid) and a condition (refuses unless replace_existing: true). However, it does not explicitly compare with alternative tools or state when not to use.

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