update_contact_report

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

The description only states 'Update', which implies modification. Annotations already indicate idempotentHint=true and destructiveHint=false, but the description adds no further behavioral context like permissions, error handling, or idempotency details.

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 concise and front-loaded, but it is too minimal. It could include more useful information without being verbose, e.g., mentioning which fields are updatable.

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 5 parameters, no output schema, and no parameter descriptions, the description is completely inadequate. It does not explain partial update behavior, required fields beyond id, or the response format.

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?

The input schema has 5 parameters with 0% schema description coverage. The description mentions only 'by ID' but provides no semantic meaning for text, subject, contact_date, or contact_type.

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 ('Update'), the resource ('contact report'), and the identifier ('by ID'). It distinguishes this tool from siblings like create_contact_report, get_contact_report, and delete_contact_report.

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?

No guidance is provided on when to use this tool versus alternatives such as create_contact_report or patch-like semantics. There is no mention of prerequisites or context for updating.

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