add_additional_party

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

Discloses idempotency, response format for fresh vs. already-linked cases, and internal handling of Capsule's 422 errors. No annotations, so description carries full burden; adequately covers key behaviors.

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?

Efficient single paragraph, front-loaded with core purpose, no unnecessary words, and well-structured progression of 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 operation, response, and error handling adequately for a 3-parameter tool with no output schema. Does not explain behavior for missing entities or limits, but generally complete.

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 67%, and the description provides contextual framing (e.g., 'kases' for projects) but does not add deep parameter details beyond the schema.

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 the verb (link) and resource (additional party), distinguishes from setting main party via update_opportunity/update_project, and references siblings like list_additional_parties and remove_additional_party.

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 states when to use this tool (adding secondary parties) and when to use alternatives (main party via update_opportunity/update_project). Lacks explicit when-not-to-use, but the context is clear.

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