zones_get_user_location

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

With no annotations provided, the description must convey behavioral traits. It describes the output but omits side effects, error conditions (e.g., what if person_entity_id is invalid), or that the operation is read-only. The description hints at no mutation but does not explicitly confirm safety.

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?

Single, tightly scoped sentence with no extraneous words. Front-loaded with the verb 'Return' and succinctly lists the output fields. Every word earns its place.

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?

Given the presence of an output schema, the description adequately covers return values but neglects input parameter guidance and usage context. It explains what is returned but not how to invoke the tool correctly (e.g., valid entity IDs). This leaves gaps for a one-param tool.

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 description does not compensate. The parameter person_entity_id is only hinted at via 'person.*' but lacks details on expected format, where to obtain the ID, or constraints. The description adds minimal meaning beyond the schema's raw type definition.

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 clearly states the tool returns specific fields (latitude, longitude, gps_accuracy, source, state) for a person.* entity. This verb+resource structure is specific and distinct from sibling zones tools (e.g., zones_get_zone, zones_list_persons_in_zone), enabling clear differentiation.

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?

No guidance on when to use this tool vs alternatives. It does not specify prerequisites, such as the need for a person entity to exist, nor does it mention when to prefer this over similar entity lookup tools like entities_get_entity or zones_list_persons_in_zone.

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