docs_search

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses two useful behavioral facts: results come back as Markdown with URLs, and no API key is required. It does not mention ranking behavior, latency, or result-count behavior, keeping it short of a 5.

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?

Two tight sentences with zero waste; the core purpose and return format are front-loaded, and the auth note is appended briefly at the end.

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?

For a two-parameter read-only search tool with annotations present and no output schema, the description covers what it does, what it returns, and that no key is needed. The main gap is the undocumented `limit` parameter and any hint about result ordering or pagination.

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 50%: `query` is documented in the schema with an example, but `limit` has no description anywhere. The description's phrase 'las páginas más relevantes' hints at result selection but never explains the limit parameter, so it adds little over the schema baseline.

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?

States a specific verb (busca) and resource (documentación de OnePlatform para desarrolladores) plus the return shape: most relevant pages with their URL in Markdown. It implicitly separates itself from docs_get_page (fetch a specific page) and api_get_operation, but never names those siblings explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of when to prefer docs_get_page for full page content or api_get_operation for API references. The only contextual note is 'No necesita claves', which is an auth fact rather than usage routing.

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