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 fully covered by structured data. The description adds no behavioral context of its own — no scope of 'overdue', no time window, no aggregation semantics, no pagination or shape of results.

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 first sentence is duplicated verbatim and the remaining content is an operation ID plus a pointer. Front-loaded yes, but the space that exists is not spent on anything that earns its place.

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 an aggregate dashboard endpoint with no output schema and two undocumented parameters, the description leaves the agent without the essential information — what 'overdue incentives' means, the data window, or how to build the query object — beyond suggesting describe_operation.

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 (query, params) are effectively opaque — 'query' is a free-form object with additionalProperties and 'params' is an empty object. The description only defers to describe_operation rather than compensating with any explanation of what can be filtered or passed.

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 endpoint path twice and adds nothing beyond what the tool name already conveys. It names no verb-object purpose (e.g., 'list overdue incentives across leases') and does not distinguish this dashboard endpoint from the many sibling dashboard tools such as get_dashboard_metrics or get_dashboard_status_breakdown.

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 the pointer that 'describe_operation provides native request schemas', which is a schema-discovery hint rather than a when-to-use rule. There is no indication of when an agent should call this instead of the other dashboard endpoints.

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