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

No annotations are provided, so the description carries the burden. It discloses that the tool returns totals for several compliance categories, which is useful behavioral context. However, it doesn't mention whether this is a read-only operation, whether it requires any permissions, or whether the summary is computed in real-time or cached. The lack of annotations makes this a moderate gap.

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?

The description is a single, well-structured sentence that front-loads the resource ('kitchen compliance summary') and then lists the specific data categories. Every word adds value, and the colon-separated list is easy to parse.

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, no-output-schema tool, the description is quite complete: it tells the agent what data will be returned. The only missing context is whether the summary is read-only and whether any filters or date ranges apply, but given the tool's simplicity, this is a minor gap.

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 the schema provides no parameter semantics. The description compensates by explaining what the summary contains, which is the only relevant semantic information. Since there are no parameters to document, a baseline of 4 is appropriate.

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: retrieving a kitchen compliance summary with specific categories (tracked intervals, not scheduled, overdue with policy risk, due this week, awaiting tags). It uses a specific verb ('get') and resource ('kitchen compliance summary'), and the listed categories distinguish it from sibling tools like list_overdue_services or get_services_due.

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 description implies this is the go-to tool for a high-level compliance overview, and the listed categories suggest it aggregates multiple statuses. It doesn't explicitly state when to use it over siblings, but the specificity of the summary categories provides clear context. No exclusions or alternatives are named, so it falls short of a 5.

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