get_broadband

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

No annotations are provided, so the description carries the full burden. It describes a read-like operation with no side effects, but does not mention potential limitations such as rate limits, data freshness, or authentication requirements. It is adequate but not rich.

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 two sentences: the first states the main purpose, the second elaborates on included data. It is front-loaded, concise, and every sentence adds value with no 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?

Given the tool has an output schema, the description covers the key output aspects (speeds, technology, availability). For a simple one-parameter lookup tool, it provides sufficient context for an agent to understand the tool's capability, though it could mention input validation (e.g., valid UK postcode format).

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% for the single 'postcode' parameter, so the baseline is 3. The description adds context about the returned data but does not add parameter-specific semantics beyond what the schema already provides.

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 it returns Ofcom broadband availability and speeds for a postcode, explicitly listing key data like download/upload speeds, technology, and availability categories. This distinguishes it from sibling tools that deal with property, crime, or demographics.

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 implies usage when broadband data for a postcode is needed, but provides no explicit when-not-to-use guidance or alternatives. Given the sibling tools are in different domains, the context is clear, but no additional usage constraints are mentioned.

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