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

With no annotations, the description carries the burden of disclosing side effects and access requirements. It uses the verb 'get,' which implies a read-only operation, and lists the data returned, but it does not explicitly state that it is non-destructive, requires no specific permissions, or has any rate limits. For a simple read summary, this is acceptable but not fully transparent about potential edge cases (e.g., does it require prior data entry?).

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 sentence that front-loads the core action ('Get the lift compliance summary') followed by a concise enumeration of what the summary includes. Every word is informative, with no redundancy or filler. It is optimally terse for a parameterless tool.

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, and a straightforward purpose—the description adequately covers what the agent needs to know to call it. It specifies the collected metrics clearly, so the expected response is inferable. However, it does not mention whether the result is a single object, list, or map, though the 'totals' phrasing implies numeric aggregates. This minor gap is acceptable given the lack of complexity.

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 no parameter schema to document. The baseline for 0 params is 4, and the description does not need to add parameter meaning since none exist. It correctly notes the absence of parameters, and no additional semantics are required.

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 states a specific verb ('Get') and a specific resource ('lift compliance summary'), then enumerates the exact components included (totals for tracked requirements, not done, overdue and citable, due this week, awaiting records). This clearly distinguishes it from siblings like search_requirements or list_citable_items, which focus on individual items rather than an aggregate summary.

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 when to use it (when you need a summary of compliance metrics) but does not explicitly contrast it with sibling tools or state exclusion criteria. For instance, it doesn't say 'use this for aggregate totals, use get_requirements_due for detailed due items.' The purpose makes it reasonably clear, but explicit routing guidance is missing.

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