Look at a 1v1 challenge

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds the useful detail that it resolves a challenge from either a URL or a number. Beyond that it says nothing about behavior on an invalid/expired challenge id, permission requirements, or whether the stake/status are live values — modest added value over the annotation.

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?

One front-loaded sentence describing the payload followed by a two-word usage cue; no filler and nothing buried.

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 single-parameter read tool with no output schema, the description's enumeration of returned fields (take, rule, sides, stake, status) effectively substitutes for the missing return documentation, and the annotation covers the safety profile. Nothing an agent needs in order to call it is absent.

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?

Only one parameter and schema coverage is 100%, with the schema already explaining 'A play.terrace.social/c/<n> link, or the challenge number.' The description restates the same link-or-number duality without adding format examples or edge-case handling, so baseline 3 applies.

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?

States a specific verb and resource ('Show a Terrace 1v1 challenge') and enumerates what comes back (take, rule, sides, stake, status), so the agent knows exactly what this retrieves. It also distinguishes itself by the identifier-based lookup ('from its link or number'), though it never names the sibling browsing tools (terrace_open_takes, terrace_challenge) it differs from.

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?

'Use before accepting' gives a concrete usage trigger that implicitly positions it against terrace_accept_challenge. There are no explicit exclusions or named alternatives for browsing/listing cases, so it stops short of a full routing statement.

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