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

With no annotations, the description carries the full burden: it discloses the access scoping rule ('workers see the checklists of the jobs they can see') and the summary payload (counts of open required items, sign-off state), which is real behavioral value. It omits whether a missing identifier means 'all visible jobs' or an error, and says nothing about result volume or pagination.

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?

Two sentences, front-loaded with the scope decision, then the access rule. Every clause carries distinct information with 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?

An output schema exists, so return-shape detail is not required and the description's mention of counts/sign-off state is supplementary. But for a two-optional-parameter list endpoint with no annotations, the missing behavior for the empty-parameter case leaves a real gap in what an agent needs to call it correctly.

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 description coverage is 0%, so the description must compensate. It does explain that a job returns both job-level and per-visit checklists while a visit narrows to that visit, which is genuine semantic content the schema lacks. However it never clarifies that both parameters are optional, nor what each does when the other is present.

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 a specific resource (checklists) and an explicit scope split: job-level plus per-visit checklists for a job, or a single visit. It clearly differs from checklists_get (one checklist) and checklists_listTemplates without naming them, so an agent can route here confidently.

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 implies the two calling modes ('checklists on a job' vs 'on one visit') but never states that both parameters are optional, nor what happens when neither is supplied. No explicit alternatives or exclusions are given, so usage must be inferred from the parameter narrative.

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