add_organization_channel

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

The description claims 'Idempotently add', but annotations set idempotentHint=false, which is a direct contradiction. This undermines trust in behavioral disclosure.

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: purpose, provider list, return behavior. Front-loaded with key information and no unnecessary 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?

Covers idempotency and return behavior for duplicates, but lacks explanation of success response and error cases. Output schema exists but is not shown; description is adequate but not thorough.

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 coverage is 100%, so baseline is 3. The description adds minor clarification for organizationId (identifying by ID or exact name) but does not significantly enhance understanding of provider or value 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?

The description clearly states the action ('add a contact channel'), the target resource ('organization'), and includes idempotency and identification method. It naturally distinguishes from sibling tools like 'add_person_channel' and 'remove_organization_channel'.

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?

The description implies when to use this tool (for adding channels to organizations) and explains idempotent behavior. It lacks explicit when-not-to-use or alternatives, but the sibling context provides differentiation.

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