Search Bundled SVG Assets

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations by specifying 'safe bundled' and 'real-world', indicating the tool returns a curated set rather than arbitrary results. It also hints at flexible search via aliases and tags, enriching behavioral understanding.

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, front-loaded sentence with no wasted words. It delivers the essential purpose and search dimensions efficiently.

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 presence of an output schema (which covers return values) and strong annotations, the description is fairly complete for a simple search tool. It adds key search dimensions and safety context. However, it leaves some ambiguity around parameter combination semantics, slightly affecting completeness.

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 only 33% (query has a description, category and provider do not). The description partially compensates by listing category and provider as search dimensions, but it does not explain their meaning, allowed values, or how they combine with query. The mapping between 'name, alias, tag' and the query parameter is ambiguous.

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 uses a specific verb ('Search') with a clear resource ('safe bundled real-world SVG architecture assets') and enumerates search dimensions ('by name, alias, tag, category, or provider'). This distinguishes it from siblings like list_themes and resolve_asset, which target different resources.

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 clearly implies usage for searching bundled SVG assets, but it does not explicitly state when to use this tool instead of alternatives or mention any exclusions. The 'safe bundled' qualifier provides some context, but no direct comparison with sibling tools is offered.

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