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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the data source (CourtListener), a cost of $0.10 USDC per call, and a verification mechanism (post-quantum signed receipt with a URL). This goes beyond the annotations and informs the agent of side effects (billing) and trust features.

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 begins with a marketing tagline ('Stratalize — governed intelligence for the agentic economy') that adds no functional value, then provides the core purpose, required param, source, attestation, and cost. It is not poorly organized but the fluff delays the key information. It is compact enough, but not every sentence earns its place.

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 single-parameter read-only tool, the description covers the main purpose, required input, output highlights, source, and cost. It lacks details about error behavior (e.g., party not found), name matching semantics, and return format, which could matter for an agent handling edge cases. It is adequate but not comprehensive.

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 compensate for the single parameter. It does clarify that 'party name' refers to 'a company or individual' seeking federal litigation history. However, it does not specify whether the name must be a legal entity name, how matches are resolved (exact vs. fuzzy), or any normalization rules. The description adds basic meaning but leaves ambiguity that could affect correct invocation.

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 a specific resource: 'Federal litigation history for a company or individual' and enumerates the output fields (total docket count, active courts, nature of suit breakdown, recent cases). It does not explicitly differentiate from sibling tools like get_docket_intelligence or get_federal_court_cases, but the 'party name' and 'company/individual' focus provides a distinct identity.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description mentions the required parameter and output fields, which implies a basic use case, but it never states exclusions or suggests other tools for related needs. Given a large sibling list with overlapping litigation tools (get_docket_intelligence, get_federal_case_law), this gap hampers correct selection.

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