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 structurally. The description adds nothing beyond that — no note on pagination, result ordering, what 'pending' means, or filtering/limit behavior — so it fails to add value beyond 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 first sentence is duplicated verbatim, which is pure waste, and the content is not front-loaded with purpose — it leads with a raw URL path rather than what the tool returns. The third clause is useful but the overall structure is filler-heavy for how little information is conveyed.

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, two undocumented parameters, and a nested free-form object; the description gives an agent nothing about return shape, pending-state semantics, or how to build the query. For a tool whose schema is this opaque, the description should carry far more burden than it does.

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% for two parameters (query as a free-form object and an empty params object). The description compensates only by deferring to describe_operation for native request schemas, which is a hint at where to find the shape but adds no semantics about what query keys or params mean for this endpoint.

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 is a verbatim restatement of the endpoint path plus an operation ID, which is essentially tautological with the name and title. It does imply a read of pending clause approvals via the URL, but offers no verb-and-resource explanation, no scope, and no differentiation from siblings like get_clause_approvals_rules or get_clause_approvals_conditional_rules.

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 use this tool versus the many clause-approval siblings, no prerequisites, and no exclusions. The only routing hint is a pointer to describe_operation for request schemas, which addresses schema lookup rather than tool selection.

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