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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; 'read-only' merely repeats the annotation. The one genuinely new trait is 'Free,' which tells the agent there is no credit cost to calling it. Otherwise the description discloses nothing about freshness, pagination, or per-scout scoping.

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 the returned content front-loaded and the cost/permission note last. No filler, no restatement of the name, nothing to trim.

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 carries the burden of describing returns, and it enumerates the three main payload areas (pipeline by stage, commissions, monthly rank), which is enough for an agent to know what it will get. Minor gaps remain, such as the time window for commissions and whether the pipeline is stage-aggregated or itemized.

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 zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly implies no inputs are needed and identifies the subject as the calling scout's own data.

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 concrete payload — scout pipeline by stage, commissions from their deals, and monthly top-scouts rank — so an agent knows what this returns. It does not, however, distinguish itself from adjacent siblings such as get_earnings or get_scout_deals, which could cover overlapping ground. Clear resource, but no sibling differentiation.

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 only usage-relevant statement is 'Free, read-only,' which signals a zero-cost, no-side-effect call but not when to choose this over get_earnings, get_scout_deals, or credit_history. There is no explicit when/when-not or alternative routing. This is a cost/permission note rather than usage guidance.

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