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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: tcosts are free on testnet and the content includes exact registration/funding steps. However, it says nothing about how the content is returned (structured doc vs. prose) or whether it changes over time, so the added behavioral value is modest.

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?

A single compact sentence plus a two-word imperative; the most actionable instruction ('Call this first.') is placed at the end as a clear call to action. The content list is dense but every item maps to something an agent needs before acting (addresses, units, costs, steps).

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-param, read-only documentation tool with no output schema, the description does the necessary work by enumerating what the returned guidance covers, including the onboarding path (register, get test funds, forecast, trade). Nothing required to invoke it correctly is missing; only the response format is left unspecified, which is minor here.

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 are no semantics to explain and the baseline of 4 applies. The description correctly avoids inventing parameters and instead uses its space to describe payload content.

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?

Enumerates the concrete resource content (network/contract addresses, units, costs, registration steps, forecasting/trading) rather than restating the title, so an agent knows exactly what it gets back. It is clearly distinct from the sibling action tools (prepare_*, submit_*, get_*), which all operate on live state. The only mild weakness is that the verb is implicit ('What Brier is') rather than an explicit 'Returns documentation about...'.

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?

'Call this first.' gives explicit ordering guidance that no sibling provides, which is exactly the routing signal an agent needs for a bootstrap/docs tool. It does not name when NOT to call it or a specific alternative, but for a one-of-a-kind onboarding tool that exclusion set is effectively empty.

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