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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real context: it resolves either a name or a userid internally and returns a specific field set, which tells the agent the call is self-sufficient rather than requiring an ID lookup first. It does not cover pagination limits or how many open jobs are returned.

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?

Three compact clauses: what it returns, when to use it, when not to. Front-loaded with the outcome, no filler, and the exclusion is placed last where it belongs.

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's enumeration of returned fields (customer, status, priority, scheduled date) is the only return-value information available, and it is present. Combined with the name/userid resolution note and the sibling routing, an agent has everything needed to invoke 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 coverage is 0% and the single 'q' property has no description, so the description carries the burden — and does so by clarifying that q accepts either a technician name or a userid. That is exactly the ambiguity an agent would otherwise have to guess at, though it stops short of format examples or disambiguation behavior for duplicate names.

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?

Names a specific verb+resource (retrieve open jobs for a named technician) and states the scope crisply: OPEN only, single technician, single call. It also enumerates what comes back (customer, status, priority, scheduled date), which lets an agent distinguish it from find_jobs, tech_workload, and unbilled_jobs_for_tech without opening any schema.

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 phrasings ('X's jobs', 'what is X working on') and an explicit exclusion: 'Do NOT use find_technicians + freeform.' It names the alternative tool chain to avoid, so both the use case and the anti-pattern are unambiguous.

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