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

No annotations are provided, so the description carries the full behavioral burden. It implies a read/status operation and lists output-like information, but it does not state side effects, permissions, failure behavior, or whether it is strictly read-only.

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 two sentences, front-loaded with the status purpose, and contains no obvious filler. Its brevity is efficient, though it leaves important details unstated.

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 27-parameter tool with no annotations and no output schema, the description is too thin. It explains the general output and input modes, but it does not sufficiently cover parameter combinations, defaults, or behavioral expectations.

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 description adds a useful input mode distinction: pass case fields directly or a caseId returned earlier. However, with 27 parameters and only 33% schema description coverage, most parameters remain unexplained in both the schema and the description.

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 gives a clear resource and scope: it reports where a case stands today, including overdue days, due reminder, next step/date, and current total. It is distinguishable from draft_reminder because it reports status rather than drafting a reminder, though it does not explicitly name the siblings.

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?

It only says to pass case fields or a caseId returned earlier, which is input guidance rather than when-to-use guidance. There is no explicit comparison to calc_claim, draft_eop, or draft_reminder, and no when-not-to-use conditions.

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