zurich_pedestrian_traffic

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

Annotations indicate read-only and open-world hints. The description adds behavioral context: data source, measurement details (direction, weather), and ordering (newest first). It does not contradict annotations and provides useful transparency beyond them.

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 concise with two short paragraphs, four sentences. It front-loads the core purpose, includes data source and method, and uses a 'Returns' section. 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?

The description covers data source, measurement, and ordering. However, it omits explicit mention of the 'limit' parameter and pagination behavior. Given the presence of an output schema (not shown), the tool is mostly complete but could benefit from parameter context.

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 description does not mention parameters, but the input schema includes descriptions for 'limit' and 'format' with defaults and constraints. Since the schema covers these details, the description adds no extra semantic value; baseline of 3 is appropriate.

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 delivers hourly pedestrian frequencies at Zurich's Bahnhofstrasse, specifies data source (hystreet.com sensors at 3 locations), and mentions measured data (number of pedestrians per hour including direction and weather). This distinguishes it from other Zurich data tools.

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?

The description provides no guidance on when to use this tool versus sibling tools (e.g., zurich_air_quality, zurich_vbz_passengers). No context about prerequisites or alternatives is given.

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