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 covered elsewhere. The description adds nothing beyond flagging describe_operation as a schema source — no pagination, filtering, or result-shape context for an unpaginated list endpoint.

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 first sentence is duplicated verbatim, which is pure waste at a length where every token should carry information. The remaining content is a single useful pointer (describe_operation), so it is both redundant and under-informative rather than efficiently front-loaded.

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?

No output schema exists, so the description should explain what the list returns and whether filtering/pagination applies; it does neither. For a nested-object, free-form-query endpoint, the only completeness it offers is the redirect to describe_operation, leaving most of what an agent needs unstated.

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 both parameters are opaque: 'query' is a free-form object with additionalProperties and 'params' is empty. The description does not explain what may be passed in 'query', so the agent must call describe_operation before it can construct a request — the definition leaves the parameter gap entirely unresolved.

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 restates the title/endpoint path ('GET /api/approvals/workflows') twice and cites an operation ID. It conveys the resource ('workflows' under approvals) but no verb-level detail about what the list contains, filters, or returns, so the agent must infer purpose from the name against ~400 siblings.

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 when-to-use guidance and no differentiation from siblings like get_approvals_workflows_by_id, get_approvals_workflows_match, or get_approvals_condition_fields. The only directional cue is the pointer to describe_operation for request schemas, which is a next-step hint rather than an invocation guideline.

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