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

The description does not disclose any behavioral traits such as pagination, rate limits, or side effects. The limit parameter is not explained, and no annotations are present to cover safety or side-effect information.

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, tight sentence that directly conveys the core function. It is free of unnecessary words or redundancy.

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 is adequate for a simple daily-retrieval tool, but it omits details like pagination behavior, the meaning of the limit parameter, and any ordering or format of results. This leaves some gaps for an agent trying to use it correctly without additional 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 adds format details for the 'ymd' parameter (YYYYMMDD), but it does not describe the 'limit' parameter, which is present in the schema. With two parameters and only one explained, the coverage is partial and the missing limit semantics create ambiguity.

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 indicates this tool retrieves all BOE items for a given date ('Every BOE item published on ymd'), which is a specific resource and action. It is distinct from sibling tools like boe_search, though it lacks an explicit verb such as 'returns' or 'lists'.

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?

No explicit guidance is provided on when to use this tool versus alternatives. It is implied that this is for daily retrieval, but there is no instruction to prefer it over boe_search for filtered queries or to use it for snapshots.

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