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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered by structured data. The description adds useful context that userid is the value to use for assignment, but says nothing about pagination behavior or total-count semantics beyond what the schema's limit parameter implies.

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 short sentences, front-loaded with the resource and followed by the most decision-relevant detail (userid for assignment) and the optional filters. No wasted words.

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?

There is no output schema, so the description carries the burden of describing returns and does so by naming userid, username and mobile. It is nearly complete for a simple lookup, missing only result-volume/pagination and any hint about the default active_only behavior's impact.

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 100%, so the schema already documents limit, search and active_only, making 3 the baseline. The description adds only the assignment use of userid and the fuzzy phrase 'search by name', which is slightly less precise than the schema's 'Match against username'.

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 verb and resource ('List technicians') plus the underlying table (fp_users) and the return fields, so the agent knows exactly what it gets back. It does not, however, differentiate itself from close siblings like nearest_technicians or technician_locations, so an agent must still infer which technician-listing tool to pick.

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 clause 'Optionally filter to active only or search by name' gives implied usage for the two filter parameters, but there is no explicit when-to-use-this-vs-alternatives guidance despite several sibling technician tools (nearest_technicians, tech_workload, technician_jobs) that could be confused with it.

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