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. The description adds nothing beyond the describe_operation pointer – no pagination, no filtering semantics, no indication of what the query object accepts.

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?

It is short and front-loaded, but the first sentence is repeated verbatim, so the description wastes its only substantive line. The operation ID is internal plumbing rather than useful content.

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?

A tool with nested free-form objects, zero schema documentation, no output schema, and no annotations covering payload shape requires the description to explain inputs and results. The description instead offloads everything to describe_operation, leaving an agent unable to call it correctly without a second round trip.

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 (a free-form `query` object with additionalProperties and an empty `params` object) are undocumented. The description does not compensate at all, merely deferring to describe_operation without describing the query syntax an agent would need.

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 restates the HTTP method and path ('GET /api/tax/parcels') twice and adds only an operation ID. It never says what a parcel is, what data is returned, or how it differs from siblings like get_tax_bills. This is effectively a tautology of the title.

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?

The only guidance is a pointer to describe_operation for native request schemas. There is no when-to-use, when-not-to-use, or comparison to any of the many sibling read tools (get_tax_bills, get_sites, get_portfolio_matrix, etc.).

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