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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that (ranking is by simulated total return, sorted best first, results include key stats), but says nothing about pagination, how the limit interacts with ranking, or what happens if fewer influencers qualify.

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 ranking metric and sort order come first. It is efficient, though it could have spent a few words explaining the mode values without becoming bloated.

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?

With four parameters, cryptic enum values, low schema description coverage, and no output schema, the description should carry more explanatory weight than one sentence. It omits what 'key stats' are returned and what the mode abbreviations mean, so an agent cannot invoke it correctly without outside knowledge.

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 coverage is only 25% (only 'inverse' is documented) and the enums WLO/LO/LS and the period values are cryptic. The description mentions 'a mode and a period' but never decodes those abbreviations or explains what mode changes, leaving the agent to guess at the most consequential parameter.

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 a specific verb and resource ('Influencers ranked by simulated total return') and states the ordering ('best first'), which clearly differentiates it from siblings like influencer or influencer_performance. It stops short of explicitly naming those siblings or contrasting itself with them, so it is clear but not sibling-differentiated.

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 text when to call rank_influencers versus influencer_performance or influencer, nor whether filtering by mode/period is required. Usage is only implied by the presence of ranking language.

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