search

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

With no annotations, the description carries the burden of disclosure. It explains return contents and the no-argument behavior, which is useful. However, it does not explicitly state whether the operation is read-only or mention rate limits or authentication, though the search nature makes these less critical. The disclosure is adequate without being exhaustive.

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, front-loaded with the core purpose, and each sentence earns its place. The second sentence adds a valuable usage tip without unnecessary detail.

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 search tool with no output schema, the description adequately explains the return values and provides a key usage example. It could mention pagination or result ordering, but the schema's limit parameter covers pagination implicitly. Overall, it is sufficiently complete for an agent to select and invoke the tool.

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?

The input schema has 100% coverage of parameter descriptions, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already provides, such as examples or parameter relationships. It does not compensate beyond the schema's 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 tool's function: search the Fivetran REST API catalog to discover endpoints. It specifies the resource (API catalog), the verb (search), and the output (method, path, summary, parameter details), distinguishing it from sibling tools that perform specific operations.

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 clear context for use (discovering endpoints) and a specific usage tip (call with no arguments to see categories), but it does not explicitly state when to use this tool over alternatives or provide exclusions. This is close to a 4 but lacks explicit sibling differentiation.

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