put_contacts_by_subject_id

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's 'Update contact' is consistent. It adds the required permission, which is helpful. However, it does not disclose whether the update is partial or full, idempotency, or side effects beyond basic mutation.

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?

The description is brief and front-loaded with purpose and permission. The <br/> and HTTP path are somewhat redundant but not excessive. Could be slightly more concise, but overall efficient.

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?

With no output schema, the description should explain return values or behavior on success. It does not mention response details or error conditions. The tool has 3 parameters and performs a mutation, so more context is needed for complete understanding.

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 100%, so the schema already documents all three parameters. The tool description adds no additional meaning beyond the schema, e.g., format for phoneNumber or structure for roles. Baseline score of 3 is appropriate.

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 'Update contact' and includes the HTTP method and path, making the tool's purpose clear. It distinguishes from sibling tools like post_contacts (create) and delete_contacts_by_subject_id (delete) through the verb and resource. However, it does not explicitly differentiate from other update tools for different resources.

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 provides no guidance on when to use this tool versus alternatives. It implies usage for updating existing contacts but does not mention scenarios or contrast with create (post_contacts) or delete (delete_contacts_by_subject_id). Missing context for decision-making.

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