search_docs

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

No annotations are provided, so the description must carry the full burden. It fails to disclose that this is a search operation returning page results; instead, it claims to fetch full content. There is no mention of pagination, result format, or any behavioral details. The description actively misleads about what the tool does.

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 short but not concise in an effective way. It mixes two unrelated instructions (fetching content and using search_docs) without clear separation. The structure is confusing and fails to front-load the actual search purpose.

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?

Despite having an output schema and simple parameters, the description is incomplete and misleading. An agent would not be able to correctly select and invoke this tool based on the description. It lacks any statement that this is a search tool, and the reference to 'doc path' is a serious omission/contradiction.

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 schema covers all parameters (query, limit, locale) with clear descriptions. However, the description instructs 'Provide a doc path (e.g. '/en/docs/official-documentation')', which does not match any parameter. A doc path is not the query parameter, and no 'path' parameter exists. This directly contradicts the schema and misguides the agent.

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 says 'Fetch the full content of a Hytale modding documentation page,' which describes a retrieval tool, not a search tool. The only hint that this is search_docs is 'Use search_docs first to find the right page path,' which is buried and contradicts the main verb 'Fetch'. The purpose is misleading.

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?

It provides a mild workflow hint ('Use search_docs first to find the right page path'), implying an alternative tool (get_doc) exists for fetching. However, it never explicitly states when to use search_docs vs get_doc, and the description itself confuses the two roles.

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