nearby_cameras

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

No annotations provided, so description carries full burden. It discloses that results are sorted by distance, which is useful behavior. However, it does not mention side effects, authentication requirements, rate limits, or that it is read-only (implied but not explicit).

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 sentences plus one example sentence. Front-loaded with purpose, then behavior, then usage. Every sentence earns its place; no wasted words.

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?

No output schema exists, but description only says 'Returns cameras sorted by distance'. It does not specify what fields are returned or pagination behavior. For a spatial query tool with 5 parameters, some details on return structure would improve completeness.

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 100%, so parameters are well-documented in the schema. The description adds context about geographic radius and sorting, but this is largely implied by the parameter names and descriptions. Little additional value beyond the schema.

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?

Description clearly states the verb 'Find' and resource 'cameras within a geographic radius'. Examples like 'webcams near Times Square' reinforce the spatial query purpose, but it does not explicitly contrast with siblings like 'search_cameras' or 'explore_cameras'.

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?

Description says 'Use for spatial queries like...' which provides clear context for when to use this tool. It does not mention when not to use it or list alternatives, but the examples are specific and helpful.

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