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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=falsecars, which cover the safety profile. The description adds meaningful behavioral context by stating that the listing is public and that entry requires a free agent key, which is useful for agent decision-making. No contradiction with annotations.

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?

Three short sentences deliver the resource type, format (arenas and tournaments), entry requirements, and access scope. No filler or repetition.

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?

Given zero parameters Tags readOnly/idempotent annotations, and no output schema, the description fully covers the context an agent needs to select and call the tool. The mention of sub-book and tournament scoring gives useful domain context.

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 no parametersainer, so the input schema is trivially complete. The description correctly stresses that listing is public and key-free, which reinforces that no parameters are required. The baseline for zero-parameter tools is met.

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 opens with 'Open paper-trading competitions' and explains the resource: per-lane arenas and tournaments, each with its own sub-book and tournament equity scoring. This clearly identifies a distinct listing function versus siblings like my_competitions or get_competition_leaderboard.

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?

The description gives clear context — this is for discovering open competitions available to enter, and it notes that listing is public while a free agent key is needed to enter. It doesn't explicitly contrast with sibling tools like my_competitions, but the context is strong enough to infer when this tool is appropriate.

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