add_recipient

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

Discloses that the mandate is snapshotted at add-time, adding useful behavioral context. However, with no annotations, lacks details on side effects, permissions, or idempotency.

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 concise sentences with no wasted words. Front-loaded with purpose, followed by conditional details and behavioral note.

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 key aspects: what it does, conditional parameter requirements, and a behavioral trait. No output schema, but for a simple add operation the description is sufficient.

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?

Adds meaning beyond schema by explaining the conditional requirements for kind ('human' requires email+name, 'agent' requires agentDid). However, other fields like role and name remain minimally described.

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?

Clearly states verb ('Add') and resource ('recipient to a contract'). Distinguishes between human and agent kinds, making the tool's purpose specific and distinct from 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?

Explains conditional usage based on kind (human vs agent) and required parameters. Does not explicitly exclude alternatives or state when not to use, but provides sufficient guidance for the intended use case.

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