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

Adds significant behavioral context beyond annotations: immediate activation, member sees but no confirmation, conditional behavior with terms. Annotations already indicate write operation (readOnlyHint=false) but description enriches with specific sequencing.

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?

Concise three-sentence structure. First sentence gives action and key detail (optional terms), second sentence describes activation behavior, third sentence clarifies conditions and alternatives. No wasted words.

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 no output schema and 3 parameters, description covers main actions and constraints. Mentions immediate activation and no confirmation. Could mention prerequisites like member existence or error cases, but sufficient for a straightforward set operation.

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 explains the required parameters (community_id, member_uid) and the optional terms parameter. Provides a concrete split example (70/30) and states omit terms means permission-only. Could detail the splits structure more, but adds good meaning.

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 verb 'Set' and the resource 'member's producer setup'. It distinguishes from sibling tools by specifying 'Members only (partners use propose_deal)', differentiating it from propose_deal and other setup-related tools.

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?

Explicitly says when to use (for members) and when not (partners use propose_deal). Explains behavior: immediate activation, member sees but doesn't confirm, omit terms for permission-only. Requires community_id + member_uid.

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