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

The description reveals that it returns metadata and public snippets, but lacks disclosure of other behavioral traits such as pagination, rate limiting, or authentication requirements. Since no annotations are present, the description carries the full burden, which it only partially fulfills.

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 is a single sentence of 14 words, which is very concise. It gets straight to the point. However, it lacks structure or bullet points that might aid readability, but overall it is efficiently written.

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?

The description is too brief given the lack of annotations and output schema. It does not explain what constitutes 'metadata' or 'public snippets', nor how the search logic works (e.g., full-text, exact match). It lacks necessary context for an AI agent to confidently select and invoke the 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 description does not provide any additional meaning for the parameters. Only the 'court' parameter has a description in the schema, while 'query' and 'limit' are undocumented. The description itself does not mention or elaborate on any parameters, leaving a significant gap.

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 action 'search' and the specific resource 'public Indian judgment and appellate tribunal metadata plus public snippets'. It effectively conveys what the tool does, though it does not explicitly differentiate from sibling tools like get_packet or statutes.search.

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?

No usage context is provided. The description does not indicate when to use this search tool versus the sibling tools. There is no guidance on prerequisites, typical use cases, or when not to use it.

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