sb_api_find

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

With readOnlyHint already indicating a safe read operation, the description adds useful behavioral detail by listing what a call sheet contains: parameters, credential, body fields, and handler caveats. It also highlights the exhaustive coverage of all 574 operations, which helps an agent understand the tool's role as a discovery layer.

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 with no filler. It front-loads the core purpose, immediately states the two invocation modes, and then gives the critical scope detail, making it easy to parse.

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?

There is no output schema, so the description compensates by naming exactly what a call sheet includes: parameters, credential, body fields, and handler caveats. Between the description and the fully documented optional parameters, an agent has enough information to use the tool correctly without additional context.

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 already documents all four parameters with 100% coverage, so the baseline is 3. The description adds value by linking 'query' to intent-based search and 'id' to call-sheet retrieval, effectively clarifying the two distinct usage modes beyond the schema's individual parameter descriptions.

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 identifies a specific verb ('Find'), a concrete resource (API operations/call sheets), and a clear scope ('Reaches all 574 operations'). It also distinguishes two modes, query-by-intent and id-based call-sheet retrieval, which is enough to separate it from siblings like sb_api_call.

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 on when to use the tool: to discover API operations by intent or to retrieve a call sheet by id. It stops short of explicitly naming alternatives or stating when not to use it, but the two-mode framing provides solid practical usage guidance.

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