Search Skeleton documentation

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

With no annotations, the description carries the burden, and it clearly says the tool searches official documentation and returns the most relevant top-level sections. It does not discuss external network access or detail limits beyond what the schema already states, but for a read-only search tool the behavior is sufficiently disclosed.

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 two sentences with no filler. The action and result are front-loaded, followed by a compact list of intended use cases. Every sentence earns its place.

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 simple search tool with fully documented parameters, the description is nearly complete: it states the resource, return type, and use cases. It could be improved by explaining how it relates to get_skeleton_section and skeleton_svelte_guidance, but nothing essential to invoking it correctly is missing.

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%, so the baseline is 3. The description adds no parameter-level detail beyond the schema, but the schema already explains query examples and the limit's min/max/default, so no compensation is needed.

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 and resource: it searches the official Skeleton documentation and returns top-level sections. It does not explicitly distinguish itself from the sibling tools, but the output type and listed topics make its purpose distinct enough for selection.

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 gives an explicit list of use cases: Svelte components, Tailwind utility classes, themes, installation, or APIs. It does not mention exclusions or alternatives like get_skeleton_section, but it provides enough context for when this search tool is appropriate.

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