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

No annotations are provided, so the description carries the full burden. It discloses the data source (IRS Form 990) and cost ($0.02/call), but does not mention read-only nature, rate limits, or potential side effects. The tool is a search, so it's likely safe, but the description does not confirm this.

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 key criteria, and includes a sample question, source, and pricing. Every word adds value with no redundancy.

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 9 parameters and no output schema, the description provides a reasonable but incomplete picture. It covers the main search dimensions but lacks details on output format, pagination (offset/limit behavior), and error handling. The financial metrics are not fully clarified (revenue vs net income).

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 description coverage is 0%, so the description must add meaning. It mentions state, NTEE code, revenue or expense range, and name, mapping to some parameters but omitting limit, offset, and net_income parameters. The term 'expense range' is ambiguous as the parameters use net_income, not expense. This lack of precision reduces helpfulness.

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 it searches nonprofit health organizations by specific criteria (state, NTEE code, revenue/expense range, name). It distinguishes from sibling tools that focus on other provider types (dialysis, hospitals, etc.) and provides a sample question for context.

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 financial profiling of nonprofit health organizations and mentions the data source, but does not explicitly state when not to use or contrast with alternatives like carecompare or hcris tools. The context from sibling names helps, but the description itself lacks explicit guidance.

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