search_collections

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool's purpose but doesn't describe key behaviors like pagination (implied by 'next_page' and 'prev_page' parameters but not explained), rate limits, authentication needs, or what the search returns (e.g., list of collections with metadata). This is inadequate for a search tool with multiple parameters.

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, clear sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 complexity of a search tool with pagination parameters and no output schema, the description is insufficient. It doesn't explain the return format (e.g., what data fields are included), how results are ordered, or error handling. With no annotations and missing output details, it leaves significant gaps for the agent to infer behavior.

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 schema already documents all parameters ('query', 'limit', 'next_page', 'prev_page') with descriptions. The description adds no additional meaning beyond what's in the schema, such as explaining how pagination tokens work or default limits. This meets the baseline for high schema coverage.

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 action ('Search for collections') and the target resource ('collections on The Noun Project'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'search_icons' or 'get_collection', which would require mentioning what makes this tool distinct (e.g., searching vs. retrieving a specific collection).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'search_collections' over 'get_collection' (for specific collections) or 'search_icons' (for icons), nor does it specify prerequisites or exclusions. This leaves the agent without context for tool selection.

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