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

Annotations already declare read-only, idempotent, and non-destructive behavior; the description adds the live-leaderboard comparison, the two input modes (pillars vs codename), and the computed metrics list. This gives useful behavioral context beyond the annotation booleans, though failure modes and data freshness are not addressed.

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?

Three sentences carry three distinct jobs: state the user question, explain the computation and output, and give the usage cue. No wasted words, and the core purpose is front-loaded.

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 no output schema, the description compensates by listing the returned metrics, including percentile, rank, distances, and strongest/weakest metrics. It also covers both input modes and the comparison scope, which is sufficient for a 6-param tool with rich annotations.

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 covers all six params with descriptions, so baseline is 3. The description adds value by grouping the four token parameters into '4 token pillars' and framing codename as an alternative input path, which is a semantic relationship not captured by the individual schema fields.

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?

Opens with the exact user question it answers ('How good am I?') and states a specific behavior: benchmark your token cascade against the live field and compare to the live leaderboard. It also enumerates the concrete outputs, making the tool's role unmistakable.

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?

Provides explicit trigger conditions: 'use it when someone asks am I a power user? or how do I compare?'. It does not name sibling tools to exclude or describe when not to use it, so it stops just short of full routing guidance.

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