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 that — no information on what the matrix contains, whether query params are required, or how large the response may be. There is no contradiction with the 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?

It is short, but the opening sentence is duplicated verbatim, which is pure waste. The one useful clause (the describe_operation pointer) is buried at the end rather than front-loaded.

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 nested-object query endpoint with no output schema, no parameter documentation, and 0% schema coverage, the description provides almost nothing an agent needs to call it correctly. The describe_operation handoff partially mitigates this, but the definition itself is inadequate.

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: an unconstrained free-form `query` object and an empty `params` object. The description does not describe either parameter, only deferring to describe_operation, so an agent gets no syntax or meaning for the filter object it must supply.

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 path verbatim, twice, without explaining what a 'critical date matrix' actually returns or how it differs from the sibling get_leases_critical_date_matrix. It is essentially a tautology of the tool name, leaving an agent to infer the resource semantics from the endpoint string alone.

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 actionable hint is that describe_operation provides native request schemas, which is a schema-lookup pointer rather than usage guidance. There is no statement of when to call this versus the near-identical leases critical-date-matrix sibling, and no mention of required context or filters.

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