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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior (it resolves a name or userid internally, and returns only open jobs with customer/status/priority/scheduled date), but says nothing about result limits, pagination, or what happens when the name is ambiguous.

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 compact sentences, front-loaded with the core purpose and return fields, followed by routing guidance and the anti-pattern. 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?

No output schema exists, so the description correctly enumerates the returned fields. For a single-parameter read tool with safety annotations it is nearly complete; only edge-case behavior (no match, multiple matches) is unaddressed.

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% and the sole parameter 'q' is undocumented in the schema, so the description carries the burden. It explicitly says q accepts a technician name or userid, which is real meaning beyond the bare string type.

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 precise verb+resource+scope: open jobs for a named technician in one call, and enumerates the returned fields. It is distinguishable from adjacent siblings like find_jobs, tech_workload, and unbilled_jobs_for_tech because it is scoped to a single named tech and to OPEN jobs only.

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?

Gives concrete trigger phrases ("X's jobs", "what is X working on") and an explicit anti-pattern: do not chain find_technicians with freeform search. Both the when and the when-not are stated, so the agent can route without inference.

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