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 core behavioral scope (returns hearings where the entity appears as a party), which is useful. However, it does not mention potential limitations, data source, or handling of edge cases like no results, leaving some behavioral details unspecified.

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?

A single, focused sentence that front-loads the essential purpose without any filler. Every word contributes meaning and the structure is immediately parsable.

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 the tool's simplicity—one required parameter, no annotations, and no output schema—the description provides adequate context for an agent to understand what the tool does. However, it could be enhanced by noting any return format or caveats, though not strictly necessary for such a direct query tool.

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?

The input schema already provides a full description of the single 'code' parameter, including its pattern and meaning. The tool description adds no additional semantic information about this parameter, so the schema carries the load and the baseline score of 3 is appropriate.

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 the tool returns court hearings where the entity is a party, making the resource and scope unambiguous. It distinguishes from sibling tools by focusing on court cases rather than ownership, real estate, seizures, etc. Though phrased as a noun phrase rather than a verb, the purpose is effectively conveyed.

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 intended use is implied by the description (i.e., retrieve court cases involving a Lithuanian entity), but no explicit guidance is given on when to use this tool versus alternatives. There are no exclusions or references to sibling tools, so the guidance is only implicit.

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