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

With no annotations, the description must carry the behavioral burden. It does disclose the access prerequisite (Pro tier and above) and the authentication requirement (Bearer token), which are genuinely useful. It does not state that the operation is read-only, whether results are cached/paginated, or what the snapshot contains, leaving meaningful gaps for a tool with zero annotation coverage.

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 clauses, front-loaded with the resource and scope, followed by the access constraints. Every sentence earns its place and nothing is wasted.

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 zero-parameter read tool, the description covers scope, tier, and auth, which may be enough to call it correctly. But there is no output schema and the description does not characterize the return value beyond 'scoreboard snapshot', so an agent cannot anticipate the metric fields or shape of the response. Adequate but with a clear gap around result content.

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 per the rubric the baseline is 4. The description does not need to explain inputs, and it adds the contextual fact that results are scoped to the caller's account, which is the only input-like dimension that matters here.

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 resource and scope: a per-(model, task_type) scoreboard snapshot for the caller's account. That is far more concrete than the bare name 'bridge_scoreboard' and distinguishes it from siblings like bridge_account_status and bridge_promotion_verdict by content. It stops short of explicitly contrasting with those siblings, so it is not a 5.

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?

It supplies two important usage conditions: Pro tier or above, and a Bearer token. However, it never says when to call this versus bridge_account_status or bridge_promotion_verdict, nor does it state exclusions. Usage is implied by the tier/auth constraints but not framed as guidance.

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