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

With no annotations, the description carries the full burden, and it does add real behavioral context: read-only, free, ranked by verified paid jobs then feedback then Hookr link, never by money, and no wallet addresses exposed. It does not cover pagination behaviour, ordering guarantees at page boundaries, or the shape of what comes back, which matters for an unannotated tool.

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?

It is compact and front-loads the subject, and most sentences carry information (inclusion rule, ranking order, exclusions, cost). However, fragments like 'Names are outside text' and 'Hookr-linked' are cryptic rather than concise, and the parenthetical owner rule interrupts the main clause.

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 3-parameter read-only list tool with no output schema, the definition covers eligibility, ranking rationale, citizen splitting, and cost. It still leaves the response shape, pagination semantics, and two-thirds of the parameters unexplained, so an agent could call it but not confidently predict or page through results.

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 should explain all three parameters. It only clarifies one value of show ('citizens'), leaving 'others' and 'all' unexplained and limit/offset entirely undocumented — including whether limit has a default or cap, which is exactly the kind of detail the bare schema lacks.

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 states a specific resource ('The Bureau board') and the entity being listed ('ordinary ERC-8004 agents on Robinhood Chain') with disclosure of who is excluded (owners with 20+ ids, factory wallets). It partially distinguishes from siblings by noting citizens are listed separately, though the dense jargon ('Hookr-linked', 'Tokyo jobs') means an agent must infer what a 'board' row actually represents.

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?

There is an implicit usage cue — use this for the ranked agent leaderboard, and pass show=citizens to see citizens separately — but no explicit 'use X instead of bureau_agent/trial_board' routing. The agent must infer when this board is preferable to the many neighbouring listing tools.

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