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

No annotations are provided, so the description carries the behavioral burden. It discloses that the operation is a server-side join, sort, and limit, and it states the default behavior ('top 10 published flows by triggers, descending'). It does not explicitly state the return shape or that no data is mutated, but for a read-style list tool the core behavior is well communicated.

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 compact and front-loaded: it opens with the core purpose, then gives usage phrases, then the routing rule, then defaults. Every sentence adds value, and there is no repeated schema information or filler.

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?

For a tool with no output schema and no annotations, the description covers the essential information for selection and invocation: purpose, metrics, defaults, and when to prefer it over siblings. The main remaining gap is the lack of an explicit statement about the response structure or fields, but the tool name and ranking semantics make the output reasonably predictable.

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 must compensate. It enumerates all metric options (triggers, completions, unique_users, button_clicks) and maps defaults for limit, metric, status, and sortOrder in one sentence. It does not name parameters explicitly, but the semantics are clearly inferable from the use cases and defaults.

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 uses a specific verb ('Rank') and resource ('flows'), enumerates the exact metrics, and gives concrete user intents like 'top N flows by X' and 'flow leaderboard'. It also distinguishes itself from list_flows/get_flow_stats by naming the preferred workflow, so an agent can select it correctly.

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?

The description explicitly lists when to use the tool ('Use for "top N flows by X"', 'best/worst performing flows', 'rank my flows', 'flow leaderboard') and gives a direct routing rule: 'ALWAYS prefer this over list_flows + multiple get_flow_stats calls'. This is clear, actionable guidance with no ambiguity.

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