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

With no annotations, the description carries the full burden, but it only says 'rankings by IPO involvement.' It does not disclose whether this is a sorted list, how the ranking is computed, what fields are returned, or any access/limitation details.

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?

At five words, the description is extremely short, but this is under-specification rather than efficient structure. It is a fragment without a verb, so it does not form a complete instruction for the agent.

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?

Although the tool is simple (no parameters, no output schema), the description still omits basic behavioral information and any differentiator from the many ranking siblings. An agent would have to guess what 'stabilizing manager rankings' means and what the returned data looks like.

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?

The tool has zero parameters, so the baseline is 4. The phrase 'by IPO involvement' provides a meaningful hint about the ranking criterion, even though there are no parameter details to clarify.

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?

The description names the resource ('stabilizing manager rankings') and the criterion ('by IPO involvement'), so an agent can infer the general subject. However, it is a noun phrase rather than a statement with a verb, and it does not differentiate this from sibling ranking tools such as get_underwriter_ranking or get_sponsor_ranking.

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 guidance on when to use this tool or which alternative to prefer. Given the large sibling set of ranking tools, an agent receives no context for selecting this over get_buyback_ranking, get_cornerstone_ranking, etc.

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