Create match template (admin)

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

Annotations indicate non-readonly and non-destructive; the description adds specific behavioral context by stating 'MUTATES live game config', which goes beyond the annotations. It could also mention side effects or permissions.

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 sentences with clear front-loading: first sentence states purpose, second explains key parameters, third gives behavioral warning. Every sentence earns its place without redundancy.

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?

Covers purpose, key parameters, and mutation warning, but lacks information about return value, required permissions, or how to handle idempotency (annotation says not idempotent). Missing parameter explanations for name and projectId.

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 only 43%, but the description explains the meaning of format (single/multi/team), outcome (how winner is decided), game (resolved by name/slug), and fields (matchmaking rules). This adds substantial value for four parameters, though name and projectId are not covered.

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?

Clearly states the verb 'Create' and resource 'match template', explaining it's the config for real-time sessions. Distinguishes from sibling create_* tools by specifying multiplayer match template and key fields like format and outcome.

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?

Explicitly warns that the tool mutates live game config and advises to 'confirm and prefer staging', providing clear usage context. Lacks explicit comparison to alternatives but the warning serves as a guideline.

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