midnight-fetch-docs

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

Annotations already indicate readOnlyHint, idempotentHint, openWorldHint are true. Description adds useful behavioral context beyond annotations: content is truncated at 15KB for token efficiency, and it's a live fetch. No contradictions with annotations.

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?

Description is well-structured with sections (common paths, usage guidance), and front-loaded with purpose. However, the list of common paths makes it slightly verbose; could be trimmed without losing value.

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 complexity, presence of output schema, and rich annotations, the description is complete. It explains function, limitations (15KB truncation), distinguishes from sibling, and provides usage context.

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 coverage is 100%, so baseline is 3. Description adds value beyond schema by listing common paths and providing usage guidance for the extractSection parameter, which helps the agent use parameters correctly.

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 tool fetches live documentation from docs.midnight.network, with a specific verb ('fetch') and resource ('docs'). It distinguishes itself from the sibling midnight-search-docs by emphasizing real-time fetching vs pre-indexed content.

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?

Provides explicit guidance on when to use this tool versus midnight-search-docs (discovery vs known pages). Lists specific use cases like latest content, specific page, and full page content. Also offers usage guidance for extractSection.

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