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

The annotations declare readOnlyHint=true, but the description adds no behavioral context beyond that. It does not explain sorting behavior, data coverage, report age handling, output shape, or any other runtime characteristics that would help an agent invoke it correctly.

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?

The description is extremely short, but this reads as under-specification rather than effective conciseness. A single noun phrase does not provide enough substance for an agent to understand the tool's purpose or invocation context.

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, yet the description does not explain what the ranking returns, how results are ordered, what period is covered, or what the rows represent. The parameter names hint at quarterly revenue data, but the description leaves all of this implicit, making the tool inadequate for correct selection and invocation.

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 input schema documents all four parameters with descriptions, so schema coverage is 100%. The description itself adds no parameter-level meaning, but the schema already carries the burden, so a baseline score of 3 is appropriate.

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 'Ranking wzrostu przychodów' is Polish for 'Revenue growth ranking' and essentially restates the tool name in another language. It does not specify what entities are ranked, what data is used, or how this differs from sibling tools like get_stock_rankings or rank_thematic.

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 versus alternatives. The description does not mention contexts, exclusions, or related tools, even though the sibling list contains several ranking and analysis tools that could easily be confused with this one.

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