midnight-fetch-docs

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

No annotations are provided, and the description does not disclose behavioral traits such as error handling, authentication requirements, or response format. It only repeats the core purpose, leaving the agent with insufficient context about what happens during execution.

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 concise, consisting of two sentences with the primary action and usage condition front-loaded. No unnecessary words or repetition.

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 lack of annotations, output schema, and parameter elaboration, the description is insufficient for an agent to fully understand the tool's behavior, return values, or error conditions. It omits critical details needed for complex usage.

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% for all parameters except path (which has a brief example in schema). The description does not mention the 'extractSection' parameter at all, failing to add semantic meaning beyond the bare schema.

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 verb 'Fetch', resource 'documentation', and specifies 'from the official Midnight docs'. It distinguishes from sibling tools like midnight-list-docs and midnight-search-docs by indicating it retrieves full content for a known path.

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 provides explicit guidance to use the tool when the specific path is known or full content is needed. It implicitly suggests alternatives (e.g., search) but does not name them directly, missing the 'when-not' aspect for a perfect 5.

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