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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description goes well beyond them: counts are grouped by comparability_group and never summed across classes, entity_id is matched exactly with padded/unpadded DUNS both resolving, there is no length cap, and results are not paginated. These are behavior traits no structured field communicates.

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-loads the usage trigger, then scopes, then parameter and bound constraints, then pagination — a logical order with no filler. Every clause (non-comparability, grouping rule, DUNS spellings, year bounds) carries operational meaning.

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-value description is correctly omitted. Scope definition, the non-comparability warning, exact-match and DUNS behavior, and fiscal-year bounds cover everything an agent needs to invoke this 3-param, all-optional tool correctly.

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%, so the description carries the full burden and does much of it: entity_id's origin ('canonical institution identifier from the institution ranking') and matching semantics are defined, and the fiscal-year bounds (1985-2100, start <= end) are given. It does not explain what a null/omitted entity_id or null fiscal years resolve to as defaults, which is the remaining 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?

States a specific resource and scope: 'what mix of award types ONE institution wins' with concrete example questions about R01s, centers, and training money. The two-scope behavior (entity-scoped portfolio vs system-wide RPG breakdown) is spelled out. It falls short of 5 only because it never mentions the closely related sibling activity_code_distribution, so the agent must infer the boundary from names alone.

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?

Opens with an explicit trigger ('Use this tool when the user asks...') and supplies three example user phrasings that map to this tool. It also warns that the two scopes are NOT comparable, which prevents a plausible misuse. It does not name a competing tool or state when another sibling should be chosen instead, keeping it below 5.

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