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

Annotations already convey readOnlyHint=true and destructiveHint=false, so the description adds value by exposing exactly what state is inspected: self-marked readiness, ban status, and judging accessibility. It does not contradict the annotations and gives useful operational context beyond the schema.

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 compact sentence carries the full purpose, lists all three checked conditions, and contains no filler. The key detail is front-loaded.

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-only check with no output schema, the description adequately captures what is being queried. It does not explicitly state the return shape, but the phrasing naturally implies the result contains readiness, ban, and judging-access indicators; mentioning this would make it fully complete.

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 coverage is 100% with team_id described as 'Id of the team,' and the description adds no parameter-level detail. Baseline 3 is appropriate because the schema fully documents the only parameter.

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 'Check' with a precise resource: team readiness. Naming the exact checks (ready to present, banned, judging-accessible) distinguishes it from generic team retrieval tools like team_get.

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 implies when to use it: whenever an agent needs a team's readiness status. It does not name alternatives or exclusion conditions, so an agent must infer that team_get or team_list would be used for general team information.

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