Search

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context: it returns lightweight result objects, not full page text, and requires a follow-up fetch call to retrieve complete content.

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 well-structured sentence that front-loads the core purpose, includes the return shape, and closes with the follow-up action. Every phrase earns its place with no wasted words.

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 one parameter, rich annotations, and an output schema, this description is complete. It tells the agent what is searched, what the result shape looks like, and what to do next to get full content.

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 0%, so the description must compensate for the undocumented query parameter. The description implies that 'query' is the search text for the public site, but it does not provide examples, syntax expectations, or any guidance on how the query is matched. This is adequate for a single obvious string parameter but not rich.

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 that this tool searches the public Sketchy Rides site and lists the content types it covers. It also distinguishes itself from the sibling tool fetch by explicitly saying that fetch(id) should be called for full page text, making its role unique.

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 clear context for when to use search — to discover pages across rental terms, fleet pages, destination guides, and blog posts — and instructs the agent to call fetch(id) for full content. It does not explicitly mention exclusions for other siblings like availability_check or quote_trip, but the search-vs-fetch workflow is clearly implied.

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