get_readings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about data update frequency ('Updated every 15 minutes'), which helps set expectations. However, it doesn't describe response format, error handling, rate limits, or authentication requirements, leaving significant gaps for a tool with 13 parameters.

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 extremely concise with just two sentences that each earn their place. The first sentence states the core purpose, and the second provides important behavioral context about data freshness. No wasted words or redundant information.

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 tool with 13 parameters and no output schema or annotations, the description is minimal but functional. It covers the basic purpose and data freshness, but doesn't address response format, error cases, or how to interpret the various filtering parameters. The schema provides good parameter documentation, but the description could do more given the tool's complexity.

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 100%, so all parameters are well-documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, but it does imply temporal filtering through 'Updated every 15 minutes,' which provides context for date-related parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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's purpose: 'Get measurement readings from all stations.' It specifies the resource (measurement readings) and scope (all stations), though it doesn't explicitly differentiate from sibling tools like 'get_measure_readings' or 'get_station_readings' which suggests similar functionality.

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 some implied usage context with 'Updated every 15 minutes,' indicating data freshness, but it doesn't explicitly state when to use this tool versus alternatives like 'get_measure_readings' or 'get_station_readings.' No guidance on prerequisites or exclusions is provided.

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