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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds useful content-level context, telling the agent this is a static rules/capability reference rather than instance data, but it discloses nothing about auth needs, limits enforcement, or freshness of the returned rules.

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 that begins with the verb 'Returns' and enumerates the payload concisely, with no filler. It could be marginally tighter, but every clause carries meaning.

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?

No output schema exists, so the description must characterize the return value, and it does enumerate the categories of content returned. Combined with full annotation coverage and zero parameters, this is nearly sufficient for calling the tool, though it never resolves the naming ambiguity between 'gift catalog' and 'custom game rules'.

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?

The tool takes zero parameters, so there is nothing for the description to document beyond what the empty schema shows. Baseline 4 applies; the description correctly implies a no-argument catalog read.

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 names a concrete return payload ('formats, capabilities, requirements and limits') and a scope ('saving custom HTML games as private drafts'), which is more than a restatement. However, it never reconciles itself with the tool name get_gift_catalog and the title 'Read custom game rules', so an agent cannot tell whether 'gift catalog' and 'custom game rules' are the same artifact. The purpose is inferable but the resource identity is muddled.

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?

There is no when-to-use guidance, no prerequisites, and no reference to any alternative. With siblings like create_custom_game, revise_custom_game, and make_game available, the description should say this is the read-only prerequisite lookup before writing a draft, but it does not.

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