Reports Update Saved Report

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

Annotations already indicate a non-read-only, non-idempotent mutation. The description only adds a vague statement about possibly creating or updating Monarch data, without clarifying upsert semantics, prerequisites, or what existing state might be affected. This does not contradict the annotations, but adds minimal behavioral context.

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 no redundant filler beyond the title-like first sentence. However, the second sentence is vague, and the overall under-specification means brevity is achieved at the cost of useful content.

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 and four parameters, the description leaves the agent without enough context about return behavior, side effects, or how this operation relates to the many sibling report tools. The schema provides some parameter detail, but the description itself is minimally informative.

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 description contributes no parameter-level meaning. Schema coverage is only 50%, and the undocumented required parameters (report_id, name) are not explained in the description; the documented fields and output_mode are already handled by 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 states a specific verb and resource—'Update saved report'—making it clear this is the update operation in the reports CRUD family. It does not explicitly contrast with reports_create_saved_report or reports_get_saved_report, and 'may create or update Monarch data' slightly blurs the update-only intent.

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 given on when to use this tool instead of reports_create_saved_report, reports_get_saved_report, or reports_delete_saved_report. The vague 'may create or update' phrase could actually mislead an agent about whether to choose update versus create.

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