Next MPC meeting

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

With no annotations provided, the description carries the burden. It fully discloses the output: the date and days until. It implies a read-only operation, though it doesn't explicitly state lack of side effects or permission requirements. However, for a simple lookup tool, this is adequate.

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?

A single, compact sentence delivers all essential information without any filler. It states both the primary output (date) and the secondary output (days until) efficiently.

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, the description provides a complete picture. An output schema exists, so return structure is presumably defined. The description covers the key purpose and output, and no further context is needed for likely use cases.

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 tool has zero parameters, and the schema coverage is 100% (vacuously). Per the rubric, a baseline of 4 is appropriate since no parameter documentation is needed. The description adds no parameter details because there are none.

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 uses a specific verb ('Get') and resource ('next scheduled Bank of England Monetary Policy Committee announcement'), plus the additional output of days until. This clearly distinguishes it from sibling tools like get_mpc_dates, which likely lists multiple dates.

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 clearly implies when to use this tool (to get the next MPC announcement date) and the context is clear. It does not explicitly mention alternatives, but the sibling name 'get_mpc_dates' suggests a different use case, and the description's specificity is sufficient.

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