fetch_latest_docs

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

No annotations provided, description carries full burden. It discloses cache bypassing, caching of fetched page, and behavior for section vs homepage. Lacks mention of potential errors or network implications, but adequate for a fetch tool.

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?

Concise paragraph with clear purpose first, then details and Args section. Each sentence adds value. Could be slightly tighter but well-structured.

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?

Covers main behaviors: cache bypassing, caching, fetching homepage or section, parameter defaults. Output schema exists so return values need no explanation. Complete for a 3-param 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?

All three parameters are well explained with examples ('introduction', 'latest') and cross-references (list_packages(), list_doc_versions()). Adds value beyond schema's basic types.

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 it force-fetches documentation from the web bypassing cache, and distinguishes from siblings by emphasizing freshness. It also specifies fetching a section or the homepage.

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?

Explicitly says use when user wants up-to-date content or stale cache. Does not list alternatives among siblings but provides context by mentioning caching behavior.

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