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

Goes well beyond the readOnly/idempotent annotations: it discloses that counts are exact only for authorized records, that ungranted sections report as unavailable rather than zero (a critical interpretation trap), that lists are paginated/capped independently, and that it never executes operational actions. This is exactly the kind of behavioral context annotations cannot carry.

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?

Four short sentences, each front-loaded with a distinct fact: when to use, count semantics, pagination behavior, safety profile. No filler.

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?

Covers usage, counting semantics, unavailable-section behavior, pagination and safety, which is strong for a dashboard tool with no output schema. The only omission is the undocumented locationId parameter, which leaves scope behavior ambiguous.

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 coverage is 0% for the single optional locationId parameter, and the description never mentions it, so an agent gets no guidance on what scoping by location does or whether omitting it widens scope. With only one optional parameter and no output schema, the gap is real but modest.

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 names specific content: authorized equipment, open work, overdue maintenance, low stock. This is clearly distinguishable from siblings like get_maintenance_cost_summary or list_due_maintenance, which return single-domain data rather than a combined overview.

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 'Use this when the user wants an interactive overview' framing gives a clear selection condition, and the contrast with drill-down siblings is implied by 'overview'. It does not explicitly name which sibling to use for detail on a specific asset or work order, but the context is clear enough.

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