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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered for free. The description adds only that the payload is aggregated statistics rather than raw records—useful but thin, with nothing about cost, caching, or freshness of the aggregates.

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?

A single front-loaded sentence naming the action and then the payload contents; no filler, no redundancy with the title.

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 no output schema, the description usefully enumerates the returned fields, which is the key thing an agent needs here. It stops short of covering the aggregate/detail alternative (get_dashboard_snapshot), which is the main remaining gap for a no-param read tool.

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?

The tool takes zero parameters, so per the rubric the baseline is 4; there is no input syntax to document or misdocument.

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?

Specific verb+resource ('Get aggregated dashboard statistics') with an enumeration of the exact metrics returned (total assets, work orders by status, overdue count, PM schedules, sites, buildings). This clearly separates it from the CRUD siblings, though it does not explicitly differentiate itself from get_dashboard_snapshot or list_dashboard_snapshots.

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?

No guidance on when to call this versus get_dashboard_snapshot or list_dashboard_snapshots, both of which sit in the sibling list and sound near-identical. The agent is left to infer that this is the cheap aggregate view and the others are detail/raw snapshots.

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