manage_account_contact

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

No annotations provided, so description carries full burden. Discloses the mutating nature (add/update/delete), required scope, and that it's a plain write. Does not mention side effects or error conditions, but for a simple CRUD operation this is adequate.

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?

Description is a single dense paragraph with efficient sentences. No wasted words, but could be slightly more structured with bullet points for actions. Still good.

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 10 parameters and no output schema, the description adequately covers the operation, links to sibling tool for ids, and explains notification toggles. Missing error handling details but otherwise 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 coverage is 100%, but description adds meaningful context: explains the action enum and which parameters are required for each action, notes that id comes from list_account_contacts, and clarifies the notification stream toggles.

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 it adds, updates, or deletes a billing/technical contact on the account. Distinguishes from sibling tool list_account_contacts which retrieves contacts, and other management 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 states required scope (account:write), explains that it's a plain write with no gating, details the three actions and their required parameters, and tells the agent that contact ids come from list_account_contacts.

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