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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no pagination behavior, no filtering semantics, no indication of response shape or size.

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 single substantive fact (the endpoint path) is duplicated verbatim in the first two sentences, wasting half the text. What remains is an operation ID of no use to an agent and a cross-reference, so it is both repetitive and under-informative.

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?

With a nested, undocumented two-parameter schema, no output schema, and no description of returned tax bill fields, the definition is not sufficient on its own. The delegation to describe_operation partially mitigates this but requires an extra 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% and both parameters are opaque ('query' is an unconstrained free-form bag with additionalProperties: {}, 'params' is an empty object). The description provides no parameter meaning at all, leaving the agent to discover them via describe_operation.

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 endpoint path 'GET /api/tax/bills' twice, which is essentially the name/title echoed back. It does not say what a tax bill is, what the response contains, or how this differs from the many sibling list tools such as get_tax_parcels.

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 guidance on when to call this versus alternatives. The only usability cue is the pointer to describe_operation for native request schemas, which is a next-step hint rather than when/when-not-to-use guidance.

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