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

The readOnlyHint annotation already signals safety, and the description confirms read-only behavior by saying it 'returns' metadata and capabilities. It adds useful scope details but does not discuss output size, formatting, or any operational constraints, though annotations reduce the burden.

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?

Two sentences pack in the tool's scope and a clear 'call this first' instruction, with the most important identifier front-loaded. No filler or repetition.

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?

For a parameter-less, read-only tool the description covers what the tool is, what it returns, and when to invoke it. With no output schema, it could have been more explicit about the returned data shape, but 'capability map (every tool, prompt, and resource)' gives a sufficient mental model.

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 in its schema, so the baseline of 4 applies; the description need not add parameter-level semantics because there is no input to configure.

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?

Identifies a specific verb and resource ('returns BedrockNews metadata') and enumerates the exact content: site description, GRIN/CLAIMS/NOVEL frameworks, terms/attribution, machine-readable surfaces, and the full capability map. This makes it easy to distinguish from sibling tools like get_article or list_stories, which target narrower data.

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?

'Call this first' provides explicit timing guidance and implies it is the discovery entry point for the API. It does not explicitly say when to prefer a sibling, but for an overview tool that is a reasonable, clear directive.

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