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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds one piece of behavioral context beyond that: the 'honest-scope card' that rides on every response, signalling what the tool's output includes. It doesn't explain rate limits, auth, or return shape further, which is fair for an orientation call.

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?

Two short sentences with zero padding, and the actionable cue ('Start here') is placed where it will be read. The phrase 'honest-scope card' is unexplained jargon, which slightly reduces standalone clarity but doesn't bloat the text.

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 parameters, no output schema, and annotations covering the safety profile, the description gives enough for an agent to know this is a safe, idempotent, first-call orientation tool that returns identity/role/scope context. Only a fuller account of what the 'honest-scope card' contains is missing.

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 takes no parameters, so the baseline of 4 applies. The description doesn't need to explain inputs and correctly focuses on what the call yields instead.

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 specific content returned: what Elo Pros is, an agent's role here, and the 'honest-scope card' accompanying every response. That is more concrete than a tautology like 'about this service'. It doesn't differentiate itself from overlapping siblings such as docs, who, or home, though the 'Start here' cue hints at orientation.

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?

'Start here' is an explicit opening-use cue, which is genuinely helpful for a zero-param orientation tool. However there is no guidance on when to return, nor any mention of alternatives (docs, who, tools) that an agent might otherwise confuse with this one.

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