get_announcement_pages

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

No annotations provided, so description carries full burden. It adds behavioral context through strategy and critical rules (e.g., default page_count of 3, max 5). However, it does not mention error handling for invalid start_page or missing local_key, nor any authorization or rate limits. Still, the provided rules are helpful and non-contradictory.

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 front-loaded with the core purpose, followed by a strategy section and critical rules. Each sentence adds value without redundancy. The Args section is cleanly organized. Length is appropriate for the tool's complexity.

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 complexity (3 parameters, output schema present), the description covers purpose, usage, and parameters well. It omits error conditions or return format, but the output schema may provide that. Slightly lacking in describing what happens on failure, but overall adequate.

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 0%, so description must add meaning. It does: local_key is 'bundle key', start_page is '1-based start page', page_count has default and max. This fully compensates for missing schema descriptions.

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 states 'Retrieve full page content for a range of pages from a parsed announcement.' This is a specific verb-resource pair, and it distinguishes from sibling tools like keyword_search (for specific facts) and download_cninfo_announcement (whole file).

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 <strategy> explicitly instructs to invoke after keyword_search provides a start_page, and to not pre-check file existence. The <critical_rules> recommend preferring keyword_search for specific facts. This clearly guides when and how to use the tool, including exclusions.

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