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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that — no pagination, response shape, scoping, or rate-limit context — and does not contradict the annotations.

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 same HTTP path sentence is duplicated verbatim, and the opaque operation ID hash consumes space without helping an agent decide or call. Front-loading is absent — the only informative clause (describe_operation) is buried at the end.

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?

For a read-only reporting endpoint with no output schema and 0% parameter documentation, the description should explain what progress data is returned and what filters apply. Instead it supplies only a route and an internal operation ID, leaving the agent unable to use the tool without a prior describe_operation call.

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% and the schema itself is opaque (a free-form 'query' object with additionalProperties and an empty 'params' object). The description does at least compensate directionally by stating that describe_operation exposes the native request schemas, but it names no actual query keys or filters, so the agent must make a second call to learn anything.

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 only repeats the HTTP path 'GET /api/approvals/progress' twice, which is a restatement of the name/title rather than an explanation. It never says what 'progress' means for approvals (per-workflow completion? pending stages? aggregate counts?), so an agent cannot tell what data it returns or how it differs from siblings like get_approvals_workflows or get_approvals_by_id_actions.

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?

There is no statement of when to call this versus the many other approvals endpoints (get_approvals, get_approvals_by_id, get_approvals_workflows_match). The only usable cue is the pointer to describe_operation 'provides native request schemas,' which hints at a prerequisite call but not at tool selection.

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