sf_search

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

No annotations provided; description only says 'ranked metric matches' but does not clarify ranking criteria, read-only nature, potential side effects, or limits. Does not disclose if it's a safe read operation or requires special permissions.

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?

Single sentence is efficient but too terse; it omits crucial details that could fit in a second sentence without being verbose.

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?

Despite having an output schema (not shown), the description leaves many unknowns: nature of ranking, pagination behavior, result format, error conditions. For a search tool with 2 parameters and no annotations, more context is needed.

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 shows 'query' and 'limit' but description provides no extra meaning. With 0% schema description coverage, the description should clarify query syntax, limit's role, or defaults. It merely implies search but no details.

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?

Description clearly states it searches SheetsFinance metrics/functions and returns ranked matches. Differentiates from sibling tools sf_describe and sf_formula, which likely serve descriptive and formula-specific purposes.

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?

No explicit when-to-use or alternatives, but the name and description imply it's for searching. Lacks guidance on when not to use or compare to siblings.

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