Search a site

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

Since there are no annotations, the description carries the burden of behavioral disclosure. It does mention the 'at once' cross-content behavior and the performance claim, but it doesn't define what counts as 'searchable content,' whether terms/formats are included by default, or how results are returned. This leaves gaps for an agent.

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, action-first, and free of redundancy. The first sentence states the core function; the second provides a practical reason for using it. Both sentences add value.

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 tool with 5 parameters and no output schema, the description provides the critical selection context (cross-content search, speed advantage over listing) but doesn't elaborate on restriction options or result pagination. The schema compensates for parameter details, making the description mostly complete, with minor gaps.

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 80% (4 of 5 parameters have descriptions), which meets the high-coverage threshold. The description adds no additional meaning to parameters like query, type, or subtype; it relies entirely on the schema. Hence the baseline score of 3 is appropriate.

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 tool's function: 'Search across all searchable content on a site at once.' It uses a specific verb and resource, and differentiates itself from list-oriented siblings by noting it's faster when the location of content is unknown.

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 explicit usage context: use this tool when you don't know where something lives, as it's faster than listing each post type. It doesn't name an explicit alternative tool, but clearly references the listing approach, offering enough guidance for selection.

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