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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral context by listing the returned fields (userid, username, mobile) and their assignment use, which is especially valuable since no output schema exists. It does not describe pagination or sorting behavior, but the core output behavior is disclosed.

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 tight sentences front-load the purpose and returned fields, then cover optional filters. Every phrase earns its place with no wasted wording.

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?

For a simple read-only list tool with full schema coverage and no output schema, the description is nearly complete: it states the resource, returned fields, and filters. The only notable gap is guidance on when to choose this tool over sibling technician tools, which is minor given the tool's straightforward listing purpose.

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 all three parameters are documented in the schema. The description restates the optional filters for active-only and name search but adds no syntax, format, or edge-case meaning beyond what the schema already provides, making the baseline 3 appropriate.

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 verb and resource ('List technicians (fp_users)') and lists returned fields. It clearly states what the tool does, but it does not differentiate itself from related siblings like nearest_technicians or technician_jobs.

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 mentions 'use for assignment' in reference to the returned userid, which implies a context, but it gives no explicit when-to-use guidance, no when-not-to-use guidance, and no alternatives for selecting a technician list versus other technician-related siblings.

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