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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine behavioral value by explaining that values are aggregated/rolled up across all task and delivery orders under the IDV, which tells the agent the numbers are pre-aggregated rather than raw transactions.

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 short sentences, front-loaded with the resource definition followed by the return payload and the ID requirement. No filler, though the identifier sentence is terse enough to leave the meaning of 'generated_internal_id' unexplained.

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?

An output schema exists, so return-shape explanations are optional, yet the description still names the aggregate fields, giving the agent enough to judge relevance. Missing only the routing guidance against the other get_idv_* tools, which is the one real gap for a single-parameter read.

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 0% and the single parameter is just named 'award_id' with no title detail. The description compensates partially by specifying that the expected value is a CONT_IDV_* generated_internal_id, which materially clarifies the required format, but it does not say the value is required or how to obtain one.

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 the resource ('Top-line amounts for an Indefinite Delivery Vehicle (IDV)') and enumerates exactly what is returned: child IDV count, child award count, child award total obligation, and base/option values rolled up across task/delivery orders. This differentiates it from per-order siblings, though it does not explicitly contrast itself with the near-identical get_idv_funding / get_idv_funding_rollup family.

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 when-to-use or when-not-to-use guidance is given. With siblings such as get_idv_funding, get_idv_funding_rollup, get_idv_children and get_idv_activity in the catalog, the agent is left to infer which of the IDV tools answers which question. Only the identifier requirement ('Pass a CONT_IDV_* generated_internal_id') is offered as a calling hint.

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