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

Annotations already cover readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add semantics beyond that. It does: results are relevance-ranked, off-topic matches are dropped, and an empty list means no on-point judgment exists — all genuinely useful behavioral context not in the annotations.

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?

Front-loaded with the core purpose, then scope, then usage examples and return shape. The enumeration of courts and multiple example queries is slightly verbose but each element earns its place by constraining scope or illustrating query style.

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?

With an output schema present and rich annotations, the description needn't explain return values — yet it usefully signals citation, court, judges, and relevance ranking plus the empty-result meaning. Complete enough for correct invocation, with only marginal gaps like the effect of combining court with year filters.

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 100%, including the court enum, limit max of 5, and year bounds, so the schema does the heavy lifting. The description reinforces query phrasing with example searches but adds nothing about the court filter, limit, or year range beyond what the schema already documents.

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?

States a specific verb and resource (find reported judgments / case law / precedents) and scopes it to named Pakistani courts, which cleanly separates it from the sibling search_statutes. An agent can tell immediately this is case-law retrieval, not statute lookup.

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?

Gives concrete trigger examples ("Supreme Court judgment on bike snatching", "precedent on specific performance") and states the jurisdiction boundary ("Pakistan only"). It does not explicitly name search_statutes as the alternative for statutory text, so the routing guidance is strong but not complete.

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