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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds a note that approval requirements are org-configurable and business workflow approvals always apply, which is useful but vague — it never says whether this specific read call can be gated or what happens if approval is required.

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?

Two short sentences with the purpose front-loaded and no filler. The second sentence is on-topic (approval gating) but slightly dislocated from the main purpose statement.

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?

Output schema exists, so return values need no explanation, and the operation is a simple single-id read. Still missing: how to source the id, behavior for a nonexistent or inaccessible report, and whether the definition is returned in rendered or raw form.

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 0%: the single required `id` parameter has no description, no explanation of the UUID format constraint in text, and no hint about where to obtain a valid id (e.g., from list_saved_reports). The description says it reads a definition but adds nothing about the identifier.

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?

"Read a saved report definition" gives a specific verb (read) and a specific resource (saved report definition), which distinguishes it from mutating siblings like update_saved_report and delete_saved_report. It does not, however, clarify its relationship to list_saved_reports, run_report, or get_report_registry, so sibling differentiation is only partial.

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 on when to use this versus list_saved_reports (enumerate), run_report (execute), or get_report_registry. The agent is left to infer from the name that this fetches a single saved definition by id.

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