search_docs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true. The description adds genuinely new context beyond those: a 50,000-character result cap, no OAuth token requirement, and confirmation it does not mutate records.

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?

Five short, front-loaded sentences with no padding; the core purpose and the routing rule come first. The final sentence ('does not change any Scalekit record') mildly duplicates the readOnlyHint/destructiveHint annotations, costing a little.

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 one-parameter search tool with no output schema, the description covers purpose, fallback behavior, result-size limits, and auth/mutation profile. Nothing critical is missing, though it says nothing about result ordering, relevance ranking, 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 description coverage is 100% for the single 'query' parameter, so the schema already carries the semantics. The description adds only 'by keyword,' which restates the schema rather than adding syntax or format guidance, so the baseline of 3 applies.

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 and resource ('Search public Scalekit documentation by keyword'), which is enough to distinguish it from the search_connectors and search_tools siblings by domain. It does not name those siblings explicitly, so sibling differentiation is implied rather than spelled out.

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?

Gives explicit routing guidance: 'Read a docs:// resource when one resource already covers the topic' and 'Use this tool only when no docs:// resource matches.' Both the when and the when-not, plus the alternative, are stated directly.

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