zones_list_persons_in_zone

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

No annotations provided; description carries full burden. 'Currently inside' implies real-time state but does not explicitly state read-only, no side effects, or any safety context. Missing disclosure of permissions or behavior on missing zones.

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 sentence, 18 words, no redundancy. Every word adds value.

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 list tool with output schema, the description covers the matching logic and scope. Lacks explanation for edge cases (e.g., empty zone), but overall sufficient given output schema.

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?

0% schema coverage, so description must compensate. It explains that the parameter is matched on friendly_name to state, adding meaning beyond the schema name. However, it does not specify the format or valid values of zone_entity_id.

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?

Clearly states the action (list), resource (person.* entities), and scope (inside a given zone, matched on friendly_name to state). Distinguishes from siblings like zones_list_zones or zones_get_user_location.

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?

Implied usage (when you need persons in a zone) but no explicit guidance on when to use vs alternatives or when not to use. No exclusion criteria or prerequisites mentioned.

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