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

Annotations already cover readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds a valuable behavioral caveat: low_stock_parts is silently [] when the account lacks Maintenance Inventory, with an explicit note that list_spare_parts handles it differently. No contradiction; this extra context justifies a 4.

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?

Two well-structured sentences. The first front-loads the dashboard contents, the second gives usage guidance and the caveat. No fluff; every clause adds value.

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 zero-parameter, read-only dashboard tool, the description is complete. It lists all return categories, states the purpose, gives the alternative, and flags the low_stock_parts edge case. No output schema exists, but the description enumerates the expected data.

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 has zero parameters, so there is nothing to explain. The baseline for 0 params is 4. The description correctly focuses on output and usage, not parameter details.

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 clearly states the tool's purpose: a whole-account maintenance overview with specific data points (counts, next due job, 10 most recent jobs, per-printer status, active plans). It uses a specific verb ('Get') and resource ('maintenance dashboard') and distinguishes itself from list_maintenance_jobs by scope and aggregation.

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?

Explicitly provides when to use this tool ('how is the farm doing') and when not to, pointing to the alternative list_maintenance_jobs for filtering, paging, or more than 10 jobs. This is clear, actionable guidance with a named sibling.

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