source_reed

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

With no annotations, the description must fully disclose behavior. It only mentions the need for an env key but omits details like pagination, rate limits, default ordering, or whether results are cached. This leaves the agent with insufficient understanding of the tool's operational characteristics.

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 two short sentences, front-loading the primary purpose. Every sentence adds necessary information, achieving optimal conciseness without sacrificing essential details.

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's simplicity (1 required param, output schema present), the description covers the basic function and required configuration. However, it lacks context relative to sibling source tools, such as any unique filtering capabilities or result structure differences. The output schema mitigates some completeness concerns.

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 parameter, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter description, which adequately documents the keyword search usage.

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 explicitly states the action ('Fetch'), the data source ('Reed.co.uk'), and the geographic scope ('UK jobs'), which clearly distinguishes it from other sibling job source tools targeting different platforms or regions.

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 guidance is provided on when to use this tool versus other source tools (e.g., source_adzuna, source_arbeitnow). The only contextual hint is the required environment variable, but no when-not or alternative recommendations.

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