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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no statement of what a 'rule' is, whether results are paginated, or what filtering is possible. For a read endpoint with annotations, a 2 reflects near-zero added 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?

Two identical sentences plus an operation-ID clause: the duplication is pure waste, and no useful information is front-loaded. It is short, but that brevity comes from under-specification rather than discipline.

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?

There is no output schema, an undocumented free-form 'query' object, and zero behavioral or return-value information in the description. Nothing tells an agent how to call this successfully or what it will get back.

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 description says nothing about the 'query' object (open-ended with additionalProperties: {}) or the empty 'params' object. With low coverage and no compensating text, the agent has no idea what to put in 'query'.

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 consists of the endpoint path repeated verbatim with no plain-English statement of what it returns. An agent can infer 'list clause approval rules' only from the URL segment, which is a tautological restatement of the title rather than an explanation.

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 when-to-use, prerequisites, or comparison against siblings such as get_clause_approvals_conditional_rules or get_approvals_rules is given. The only guidance is a pointer to describe_operation for native schemas, which is a schema-discovery hint rather than usage guidance.

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