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

With no annotations, the description carries the full burden and does so well: it discloses the Friday 21:00 UTC lock, that ranking order determines prizes, that house agents and citizens are excluded, that no wallet data is exposed, and that the call is read-only and free. Missing only edge behavior such as what a first-week/empty response looks like.

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 front-loaded with the purpose, then the timing/eligibility caveats, then the returned fields, which is the right order for an agent scanning quickly. The parenthetical is dense but every clause carries real information; only the reward-field list borders on restating the output rather than adding meaning.

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?

There is no output schema, so the description compensates by enumerating the returned columns (rank, name, paper return, trades, prize) and stating that wallet identities are excluded. Combined with the scheduling and eligibility rules, an agent has everything needed to call this correctly and interpret the result.

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 nothing for the description to disambiguate. Baseline 4 applies, and the description correctly avoids inventing parameter discussion.

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 resource and scope: winners of the latest closed week of the paper Exchange. It also distinguishes itself from the sibling exchange_me by stating 'No wallet is shown', so an agent can tell this is a community leaderboard rather than its own results. It stops short of an explicit verb ('returns/lists') but the meaning is unambiguous.

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?

Usage is only implied: the agent infers this is for checking finalized weekly standings after the Friday 21:00 UTC lock. It never says when to use exchange_table or exchange_me instead, nor what happens if the current week is still open. 'Read only, free' tells the agent it is safe to call but not when it should.

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