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

Annotations only cover the read-only/idempotent/closed-world profile; the description goes well beyond that by disclosing the shape of the answer (instruments, why each applies, a caution flag, next deadline) and by calling out edge-case behavior for entity classes with no applicable instruments. That is exactly the return-contract detail an agent needs since there is no output schema.

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?

Two sentences, front-loaded with the input-to-output mapping, and the second sentence handles exceptions. The clause chain in sentence two ('why each applies, a caution..., and its next dated deadline') is dense but each clause conveys a distinct output field, so little is wasted.

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 no output schema, the description carries the full burden of describing the return value, and it does so precisely, including the per-class exception behavior. Nothing an agent needs to select or call this three-parameter tool correctly is missing.

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% and the schema already explains the regulatory consequence of each flag (LODR disclosure, DPDP). The description restates the same three inputs without adding syntax, defaults, or interaction rules, so the baseline 3 applies.

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 gives a specific verb ('returns') plus the exact inputs consumed (entity class, listed status, personal-data handling) and the exact payload produced (binding instruments, reasons, misapplication caution, next dated deadline). The Indian scope cleanly separates it from the sibling find_global_cyber_regulations without needing to name it.

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 preconditions for calling are clear from the enumerated inputs, and edge-case guidance is given (RBI classes map to their own 2026 Directions; RRBs and LABs have none and the result says so). It never explicitly states when NOT to use it or points to a sibling tool for out-of-scope cases, so it stops short of a 5.

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