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

Annotations cover the read-only profile, and the description adds meaningful non-schema behavior: results are limited to people within the caller's location access, with admins seeing everyone. That permission-scoping detail is genuinely useful and not derivable from annotations or schema, though staleness/freshness beyond the within_hours window is not discussed.

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 short sentences, front-loaded with the resource and the returned fields, and the access-scoping caveat is placed appropriately as a qualifier. No padding.

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?

With no output schema, the description usefully names the returned fields (position, time, battery, accuracy), which is the information an agent would otherwise lack. The main remaining gap is the undocumented user_ids parameter and lack of sibling differentiation.

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 only 50% (user_ids has no description) and the description never mentions either parameter or how filtering works. 'Each person's latest position' hints at per-user behavior but does not explain user_ids or the recency window, so it fails to compensate for the coverage gap.

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 concrete resource (technician locations) and enumerates the specific fields returned: latest position, time, battery, accuracy. It does not explicitly differentiate from nearby siblings like nearest_technicians or technician_route, so it falls short of a 5.

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?

There is no statement of when to use this versus nearest_technicians, technician_route, or technician_jobs, which all sound overlapping. The only guidance is the scoping note about location access, which is eligibility rather than usage context.

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