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 by structured data. The description adds nothing beyond a note that schemas live behind describe_operation — no filtering behavior, pagination, or auth/scope 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?

The same sentence appears twice, which is pure waste, and the useful hint about describe_operation is buried after the duplication. It is short but under-specified rather than concise.

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 wrapper endpoint with no output schema, undocumented nested query params, and generic annotations, the description should at least characterize the returned collection or accepted filters. Pointing to describe_operation is the only bridge, leaving the agent unable to call it correctly without a follow-up tool 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% for two parameters (a free-form 'query' object and an empty 'params' object), so the description must compensate and does not. It only redirects to describe_operation for the native request schema, which is a pointer rather than semantics for query/path filtering.

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 repeats the endpoint path 'GET /api/compliance-rules' twice, which merely restates the name and title rather than explaining what the call returns or its scope. An agent can infer it retrieves compliance rules, but nothing distinguishes a list endpoint from a search, and no sibling (e.g. get_compliance_rules_by_id) is referenced.

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 get_compliance_rules_by_id or execute_read. The only actionable pointer is 'describe_operation provides native request schemas', which tells the agent how to fetch a schema, not when this operation applies or what constraints it has.

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