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

With annotations already declaring the safety profile (non-read-only, closed-world, not idempotent, not destructive), the description adds real value: re-validation by the local Rust compiler, a disabled-by-default state, and the strong auth note that operator identity comes only from the server environment and never a model token. These are non-obvious behavioral facts an agent needs.

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 compact sentences, front-loaded with the core action and followed by validation and identity caveats. No wasted padding, though the identity sentence is slightly compressed.

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?

An output schema exists so return values need not be described, and the safety/auth context is covered. But for a mutation tool with 8 undocumented parameters and no idempotency guidance (annotations say not idempotent, so duplicate-submission behavior matters), the definition leaves the agent under-informed about how to call it.

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 0% across 8 parameters, and the description documents none of them. It implies 'source' holds GardenScript and that the target is an arena, but arena_slug, entrant_name, and the five provenance fields (model_name, model_version, prompt_sha256, transcript_sha256, model_provider) are entirely unexplained.

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 (submit) and resource (externally generated GardenScript to an arena), so the agent knows it is a write/registration action. It does not explicitly differentiate from siblings like validate_gardenscript or strategy_seal, which handle the related validate/seal phases.

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 'Disabled by default' note provides one important precondition for invocation, and 'externally generated' hints at a context. However, it never states when to use this versus validate_gardenscript/strategy_validate, nor does it describe what happens on a successful submission, leaving usage largely inferred.

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