law.attorney-lookup

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

No annotations provided, so description carries burden. Discloses case-insensitive Title-Case + startswith matching and return fields (firm name, contact info, CL IDs). Does not mention pagination or limit behavior.

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?

Three sentences with clear structure: purpose, output, usage condition. No wasted words.

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?

Covers purpose, parameters, matching, and return fields. No output schema, but description compensates well. Could mention data source (CourtListener) and what CL IDs represent, but overall sufficient.

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?

Adds meaning beyond schema by clarifying that at least one of name or firmName is required and describing matching behavior. Limit parameter is not mentioned in description, though schema coverage is 67%.

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?

Explicitly states 'CourtListener attorney search by name and/or firm' with specific verb and resource. Distinguishes from siblings like law.judge-lookup and law.case-search by focusing on attorneys.

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?

Provides clear precondition: 'Supply at least one of name or firmName'. Does not explicitly exclude alternatives or provide when-not-to-use guidance, but context among siblings implies appropriate use.

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