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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses the specific categories of totals returned, which gives insight into the tool's output. However, it does not explicitly state that this is a read-only operation, nor does it mention any potential side effects, limitations, or additional behavior. For a simple getter, the category enumeration is helpful but not exhaustive, so a score of 3 is appropriate.

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 primary action and resource, followed by a colon and a concise list of the summary categories. Every word earns its place, with no redundancy or 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?

Given the tool's simplicity (no parameters, no output schema), the description provides a reasonable level of completeness by listing the categories that the summary covers. It could be more complete by explaining how the totals are computed or what units are used, but for a summary getter, it is sufficiently clear for an agent to understand the tool's purpose and expected output.

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 input schema is empty, so there are no parameters to describe. The baseline for a tool with zero parameters is 4. The description adds no parameter information because none is needed, but it does not need to compensate for schema gaps.

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 with a specific verb ('Get') and resource ('kitchen compliance summary'), and enumerates the exact categories included (tracked intervals, not scheduled, overdue with policy risk, due this week, awaiting tags). This distinguishes it from sibling tools like list_overdue_services and get_services_due, which focus on listing specific services rather than aggregating compliance totals.

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 does not provide any guidance on when to use this tool versus the sibling alternatives. It only states what the tool does, without mentioning contexts, prerequisites, or exclusions. For example, it doesn't say 'use this for a high-level overview instead of listing individual services.' This leaves the selection decision to the agent without explicit direction.

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