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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, what the response format is, whether results are paginated, or any limitations. The phrase 'who ministers have met' is too vague to convey the actual output structure or side effects.

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 very concise—two short sentences with no fluff. It front-loads the topic and quickly covers filters. The first sentence is a grammatical fragment ('Ministerial transparency releases, who ministers have met') but it is still skimmable and efficient. Overall, it is appropriately sized.

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 tool is relatively simple (two optional filters), but with no output schema or annotations, the description should provide more context about the returned data or any constraints. It only offers a vague statement about meetings and does not mention that both parameters are optional or what happens when no filter is provided. The description is incomplete for an agent to fully understand the tool's behavior.

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 names both parameters ('minister' and 'organisation') and indicates they are for filtering, adding some meaning to the bare string schema. However, it does not specify whether they are optional, how they interact, or expected value formats. Given the schema description coverage is 0%, the description provides partial compensation but is insufficient.

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 identifies the tool's purpose: it deals with ministerial transparency releases and records of who ministers have met. The filter options by minister or organisation further clarify the scope. While it lacks an explicit verb in the description itself, the title 'Search ministerial meetings' and the filter guidance make the purpose clear and distinguishable from sibling tools like search_ministerial_gifts.

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 gives no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. The only hint is 'Filter by minister or organisation', which explains how to narrow results but not when this tool is the appropriate choice among siblings. There is no explicit comparison or recommendation.

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