midnight-search-docs

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

No annotations are provided, so the description must fully disclose behavior. It only states the tool searches content, but does not mention pagination, result format, search capabilities (e.g., fuzzy search), or limitations. This leaves significant gaps for an agent.

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 a single concise sentence that front-loads the action. However, it could be slightly more structured by separating usage guidance, but current length is appropriate.

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 nested schema, three parameters, and the presence of multiple sibling doc tools, the description is too minimal. It does not explain return values (no output schema) or how parameters like category and limit affect results, leaving the agent underinformed.

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?

The input schema has three parameters (query, category, limit) with only the query having a description. The description adds no additional meaning or examples for any parameter, failing to compensate for the low schema coverage (0% per context).

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 searches Midnight documentation content for guides, API docs, and conceptual explanations, providing a specific verb and resource. It distinguishes from sibling doc tools (like fetch, list, sync) by focusing on search functionality.

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 with 'Use for finding...' but does not provide explicit guidance on when not to use or alternatives. Sibling tools exist (e.g., midnight-fetch-docs, midnight-list-docs) but are not mentioned.

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