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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds substantial non-obvious behavior: the total-matches-country rule for detecting non-local lists, total_pages/has_more pagination, not-found error past the last page, and empty items for a genuinely empty Events feed.

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?

Front-loaded with purpose and outputs, then parameter sourcing, then behavioral nuances. Dense but each clause carries real information; only the local-vs-country explanation is slightly verbose.

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 an output schema present, return-value explanation is not required, yet the description still covers pagination, error, and empty-feed behavior for a single-parameter fetch tool. Complete enough for correct invocation.

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 description coverage is 100%, so baseline is 3, but the description goes further by clarifying accepted URL forms and the pagination query embedded in the URL, adding meaning beyond the schema's own text.

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?

States a specific verb and resource (fetch one BBB newsroom page), enumerates the outputs (story cards, result count, page metadata), and distinguishes itself from siblings by naming bbb_news_topics and bbb_local_bbbs as URL sources.

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?

Gives clear context: where the URL comes from (national topic, regional newsroom, or a chapter's news_url) and how to paginate by appending page=N. It explains the local-vs-country behavior but doesn't state when NOT to use this tool versus a sibling news fetch.

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