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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety and idempotency are covered. The description adds genuinely useful behavior beyond them: results reflect a *live* count of only ACTIVE tenders, the portal surface is one of several distinct government sites, and it is framed as a discovery/selection step feeding another tool.

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 resource and its scope, followed by three concrete example queries and a single routing sentence. No filler or restatement of the tool name; every clause adds selection or invocation value.

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?

There is no output schema, and the description compensates by stating what each record contains (organisation plus live active-tender count) and which portals are covered. Minor gaps remain — no mention of result ordering, result limits, or what happens for a portal with no matches — but the essential contract is clear.

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 the portal enum values and the query substring filter are already fully documented in the schema. The description adds only an illustrative example ('biggest buyers on Maharashtra e-tenders') and implies the substring filter's purpose; this is the baseline case where the schema does the heavy lifting.

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?

Specific verb (lists) plus resource (buying organisations on named Indian government e-procurement portals) and a distinguishing scope: each org is returned with its live count of ACTIVE tenders. The example queries ('how many active tenders does the Indian Army have') make the output shape unambiguous and separate it from sibling india_search_tenders, which returns tenders rather than buyers.

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?

Explicitly routes the agent: 'Use it to pick an organisation for india_search_tenders,' which names the downstream sibling and the condition that selects it. There is no statement of when-not to use it (e.g. when you already know the org name and can skip this step), so it falls just short of the full 5.

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