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

Annotations declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds useful return-field details and the filter logic (completed/closed, no invoice, one technician, date range), but says nothing about authentication, pagination, date inclusivity, or default behavior when dates are omitted.

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 tightly written sentences with no filler. The core scope is front-loaded, and the second sentence efficiently enumerates the return fields without redundancy.

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?

The description covers purpose, scope, and return fields, and annotations handle read-only status. For a simple query tool this is mostly sufficient, but missing details about date semantics, optional parameters, and result limits leave operational gaps.

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?

With 0% schema description coverage, the description must compensate. It adds meaning beyond the schema by indicating that technician selects exactly one technician and that from_date/to_date define a date range. However, it does not specify date formats, which date field the range applies to, or that the date parameters are optional.

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?

States a specific resource (completed/closed jobs with no invoice) and scope (ONE technician, date range), and lists the returned fields. It partially differentiates from siblings like unbilled_completed_jobs by emphasizing the single-technician focus, but does not explicitly name or contrast with alternatives.

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 the tool is for finding unbilled jobs for one technician, but offers no explicit when-to-use or when-not-to-use guidance. It does not name alternative tools such as unbilled_completed_jobs or technician_jobs, leaving selection to inference.

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