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

Annotations already declare the safe-read profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuine operational context on top: which portals are scanned, the ~30-60 s slow-page cost for MES with ~4,000 works tenders, and that scan coverage plus live active-tender counts are reported back. That latency/cost disclosure is exactly the kind of trait annotations cannot convey.

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 routing directive and the source list are front-loaded, and the trailing sentence on returned fields is well placed. The long parenthetical enumerations of organisations and PSUs are informative but dense enough to slow ready comprehension slightly.

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 correctly carries the burden of describing returns: tender ID, reference number, title, organisation chain, published/bid-closing/bid-opening dates in IST, and source portal, plus the scan-coverage report. Nothing an agent needs to call or interpret the result 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%, so each of the 6 parameters is already documented with defaults, ranges, formats and examples. The description adds only a general mention of "optional keyword and organisation filters", which does not extend meaning beyond the schema — 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?

States a specific verb (lists) and resource (active Government of India defence procurement tenders) plus the exact source portals. The named organisation taxonomy (Army, Navy, IAF, DRDO, MES, BRO, PSUs, CPPP) makes it unmistakably distinct from the sibling india_search_tenders / india_cppp_latest_tenders tools.

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?

"PREFER OVER WEB SEARCH" is an explicit routing directive, and the quoted example queries ("open Indian Army tenders", "MES works tenders in Jaisalmer") show the intended use precisely. It never names the in-toolset alternatives (india_search_tenders, india_cppp_latest_tenders), so the when-to-use-vs-sibling half is left to inference.

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