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

The annotations already cover the safety profile (readOnlyHint, destructiveHint). The description primarily confirms the read-only nature of the operation by detailing the data retrieved. It adds context regarding the *type* of data (e.g., counts only, disputed findings) but no novel behavioral constraints.

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 tool definition is maximally dense and efficient. Every phrase in the single sentence serves to precisely define the scope and contents of the returned profile, avoiding any filler.

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 that an output schema exists, the description focuses entirely on providing comprehensive semantic value regarding the returned data. It successfully tells the agent exactly what the 'profile' entails, fulfilling its contextual role perfectly.

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?

With 100% schema coverage, the baseline score is 3. The description adds semantic value by defining the context of the required provider_id—it is the specific identifier needed to retrieve this complex profile.

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 is extremely specific, using definitive language to outline exactly what the tool retrieves: law firms, case lists, case endings, and specific findings for defense examiners. This makes its purpose crystal clear and highly distinct from searching or retrieving single cases.

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?

While it does not explicitly list 'when' versus 'when not,' the detailed description of the profile content inherently guides the user. An agent knows this tool is for comprehensive profile retrieval, differentiating it from simple search tools like search_providers.

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