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

Discloses return fields (case count, compensation rate, main vaccines, firm) which adds behavioral context. No annotations provided, but description is adequate for a read-only search operation. Does not mention safety or side effects.

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?

Two concise sentences: first states purpose, second adds return details and use case. No unnecessary words, well-structured.

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?

Provides enough context for a simple search tool with no output schema and two parameters. However, the 'limit' parameter is left unexplained, and ordering/pagination behavior is missing.

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 0%, so description must compensate. 'Search by name' only partially explains the 'query' parameter; the 'limit' parameter is entirely undocumented with no default explained.

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 'Search petitioner attorneys and firms by name' with a specific verb and resource. It distinguishes from siblings like 'search_cases' and 'get_attorney' by focusing on aggregate stats.

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?

Explicitly mentions usefulness for 'who has handled X cases' questions, providing context for when to use. Lacks explicit guidance on when not to use or alternatives.

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