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

With no annotations, the description carries the full burden and does well: it discloses that the active version is what plays in a cup, that theater entries are smoke-tested against that theater's rules first, and that a failure returns an explanation of what the theater requires. It omits whether an enrolment can be withdrawn, permission requirements, and any rate limits.

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 front-loaded sentence with no filler, and the cup-versus-theater contrast is presented in parallel structure. The nested parentheticals make it dense but every clause conveys real behavior.

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?

Behavioral coverage is strong for a mutation tool with no annotations and no output schema, and the pre-validation/error-explanation detail is exactly the kind of context an agent needs. However, with three parameters at 0% schema coverage and no description of 'key' or accepted ladder values, an agent still cannot construct a correct call from this definition alone.

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 0%, so the description must compensate and it largely does not. It implies 'ladder' is the cup or theater identifier and 'bot' is the bot being entered, but the required 'key' parameter is never mentioned and no format or accepted-value guidance is given for any of the three.

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 gives a specific verb (enrol) and two concrete target resources (cup, theater preview), which clearly separates it from read-only siblings like get_cup or list_ladders. It falls short of a 5 because the term 'ladder' — the actual required parameter and tool name — is never tied to 'cup' or 'theater preview', so the agent must infer that the ladder identifier is one of those.

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?

It explicitly states the selection rule between the two modes: cups allow one bot per account while theater previews allow several. It does not address when to prefer this over siblings such as scrimmage or upload_version, so a clear context is given but not a full alternative map.

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