Find Locations

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

No annotations are provided, and the description does not mention whether the tool is read-only, has side effects, permissions, or any limitations. Since the description is the only source of behavioral information, this is a significant gap.

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?

The description is a single, short sentence that immediately conveys the tool's purpose without verbosity. It is appropriately concise, though it could include a bit more context without becoming wordy.

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?

While an output schema exists, the description fails to provide any context about how the tool fits into the broader set of siblings, what kind of results to expect (beyond 'locations' and 'people counts'), or when it should be preferred over alternatives. The lack of usage context makes it incomplete for an agent to decide when to invoke it.

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?

The schema covers 100% of parameters with the description 'Location search query', which gives basic meaning to the single parameter. This meets the baseline for a well-documented schema, but the description does not elaborate on expected format, examples, or potential values beyond 'query'.

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 verb 'Find' and the resource 'office locations' with 'people counts', making the primary purpose understandable. It does not explicitly distinguish it from similar tools like get_people_at_location, but it is specific enough to convey the core intent.

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 guidance on when to use this tool versus its siblings, such as get_people_at_location or search_people. The description lacks any context about filtering, search behavior, or typical use cases, leaving the agent to guess.

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