league_table

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds nothing beyond purpose. It does not say how volume is aggregated, how ties are ordered, or whether the ranking is recomputed over the supplied date window versus all-time.

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?

A single front-loaded sentence with no filler; the verb and ranked entity come first and the domain term is clarified in parentheses. Nothing 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?

An output schema exists so return values need not be described, and the annotations cover the read-only profile. For a tool with five optional filters and no required parameters, the main remaining gap is how those filters interact with the ranking, which is modest.

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 all five parameters (rite, limit, last_date, asset_type, first_date) are already documented in the schema. The description adds no additional meaning, such as how the date bounds constrain the ranking window; baseline 3 applies when the schema carries the burden.

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 and resource ('Rank lead underwriters') plus the ranking metric ('total offering volume') and disambiguates the concept with the parenthetical 'ECM/DCM league table'. It is clearly distinct from siblings such as issuance_volume or rank_funds, though it never names an alternative to contrast against.

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?

There is no when-to-use or when-not-to-use guidance. An agent cannot tell from the description how this differs operationally from issuance_volume or search_offerings, nor whether filters must be paired (e.g., first_date with last_date) to produce a meaningful ranking.

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