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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value beyond them by flagging that the numbers are 'Live' (i.e., current rather than cached or historical) and by enumerating the payload, which matters because no output schema exists.

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 front-loaded sentence led by the key qualifier 'Live numbers', with the metric list earning each word by telling the agent what will come back. No filler, no repetition of the title.

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?

With no output schema, the description must carry the burden of describing returns, and it does so by listing every metric including per-region counts. It stops short of indicating the response shape (flat object vs. nested per-region map) or whether figures are scoped to a market, which is a modest residual gap for an aggregate tool.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description correctly implies no input is needed.

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 enumerates exactly which catalogue metrics are returned (open calls, closing-in-30-days, grants, budget, remote jobs, places, per-region counts), so the resource is unambiguous even without an explicit verb. It does not, however, distinguish itself from siblings like catalogue_trends or closing_soon, whose names overlap with the metrics listed here.

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?

There is no statement of when to call this versus catalogue_trends (historical?) or closing_soon (the same 30-day closing metric is listed here), and no prerequisites or exclusions are given. The word 'Live' weakly implies a real-time snapshot in contrast to a trends tool, but that is inference rather than guidance.

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