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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful domain context (test-USDC prize pool, scoring rubric) but says nothing about result ordering, pagination, or how the `mine` filter behaves without a key.

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?

Two compact clauses, front-loaded with the resource definition before filter options. It is telegraphic (the fragment 'status: ...; mine: ...') but no sentence is wasted.

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 simple zero-required-parameter list tool with full schema coverage and no output schema, the description covers the essentials. However, with no output schema present, an agent gets no hint of what a returned competition record contains beyond the prize-pool and rubric mention.

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 100% and both enumerated parameters are documented in the schema itself, so the description's restatement of 'status: open, judging, finished or all; mine: created or entered' adds almost nothing. Baseline 3 applies when the schema already carries parameter meaning.

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 title 'Find competitions' plus the description 'Challenges with a test-USDC prize pool and a scoring rubric' identify a specific resource and its defining traits, distinguishing it from sibling mutations like competition_create and competition_enter. It lacks an explicit verb such as 'list', but an agent can still tell this is the enumeration endpoint.

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 enumerates the filter values for status and mine, which implies how to narrow results, but it never states when to use this tool versus competition_get or competition_enter. Usage is inferable from the filter list rather than explicitly guided.

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