Fetch latest Self protocol documentation from GitHub

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds useful context beyond this by specifying the source ('GitHub') and the freshness guarantee ('latest'), but does not disclose other behavioral traits like rate limits, authentication needs, or response format details. No contradiction with annotations 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?

The description is front-loaded with the core purpose in the first sentence, followed by supporting details in a structured list of topics. Every sentence earns its place by enhancing clarity without redundancy, and the bulleted list efficiently organizes information without unnecessary verbosity.

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 tool's low complexity (read-only, two parameters), high schema coverage (100%), and the presence of an output schema (implied by context signals), the description is complete enough. It covers purpose, source, freshness, and available topics, addressing all necessary context without needing to explain return values or redundant schema details.

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 the schema fully documents the 'topic' and 'section' parameters. The description adds value by listing available topics (e.g., 'quickstart', 'backend-sdk'), which clarifies the 'topic' parameter's semantics beyond the schema's enum-like list, but does not provide additional details on 'section' or parameter interactions.

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 the specific action ('fetch', 'retrieves') and resource ('Self protocol documentation from GitHub'), distinguishing it from siblings like 'search_docs' (which likely searches within docs) or 'list_docs_topics' (which likely lists topics). It explicitly mentions 'latest' to highlight freshness, setting it apart from static documentation tools.

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 description implies usage for obtaining up-to-date documentation, but does not explicitly state when to use this tool versus alternatives like 'search_docs' or 'list_docs_topics'. It provides clear context (e.g., 'ensuring you always have the latest information') but lacks explicit exclusions or named alternatives.

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