find_cells

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool mutates state, what the return format is, or performance implications. For a tool with no annotations, the description should clearly indicate its side effects, but it does not.

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 sentence, which is concise, but it lacks structure and is too brief to convey sufficient information. It is not front-loaded with critical details; it merely states the basic function.

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?

Given no annotations, no output schema, and 4 parameters, the description is very incomplete. It does not explain return values, behavior with regex, or how cellType filtering works. The tool is contextually incomplete for an agent to use effectively.

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 0% description coverage for its 4 parameters. The description only mentions 'by source or output text' but does not explain how parameters like 'query', 'regex', 'cellType', or 'includeOutputs' function. This leaves the agent without necessary understanding of parameter behavior.

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 finds cells by source or output text, which is a specific verb-resource combination. It distinguishes from sibling tools like 'get_cells' which likely retrieves all cells without filtering. However, it could be more specific about what 'by source or output text' means exactly.

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 guidance is provided on when to use this tool versus alternatives like 'get_cells' or 'search_cells'. There are no prerequisites or contextual hints for when this tool is appropriate.

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