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

The description explicitly states 'Read-only,' which is a key behavioral trait, especially in the absence of annotations. It also mentions the data source. However, it does not disclose other behaviors like pagination, sorting, or result limits, which are relevant for a search tool.

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 extremely concise, consisting of two sentences that cover the core action, data source, filter options, and read-only nature. Every word adds value with no waste.

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 4 optional parameters and no output schema, the description adequately covers purpose, source, and safety (read-only). However, it lacks details on result format, ordering, or how to drill down (e.g., use get_firm for details). This leaves minor gaps in completeness.

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 coverage is 100%, meaning each parameter already has a description. The tool's description reiterates the filter criteria without adding new semantics, examples, or constraints beyond what the schema provides. It neither enriches nor contradicts the schema.

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 searches a directory of SOC 2 audit and compliance-readiness firms and lists specific filter criteria. It distinguishes itself from siblings like get_firm (which likely retrieves a single firm) by focusing on listing/search behavior.

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 implies usage for finding firms by framework, ecosystem, partner status, or category. However, it does not explicitly state when not to use this tool (e.g., when a single firm is needed, use get_firm) or provide explicit alternatives.

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