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

Goes far beyond the annotations (which only declare destructive/idempotent/openWorld). It discloses specific error behavior (400 manifest_invalid names the offending path, 409 immutable), the exact immutability rules (scored board keeps id/sort/unit/format, unlocked achievement keeps id and points, min_trust only increases, retire instead of removing), admin-only arena boards, and the authorization model.

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?

The opening sentence is front-loaded and the tool's purpose leads, with constraints after. The manifest spec is a dense run-on with heavy parenthetical nesting that is hard to scan, but almost every clause carries necessary constraint information, so little is wasted.

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 tool with no output schema and a deeply nested manifest object, the definition is complete: it documents the return shape ({rev}), all nested fields and their constraints, immutability/error semantics, and auth. Nothing an agent needs to invoke it correctly is absent.

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?

Although schema coverage is 100%, the schema's manifest property merely delegates ('see the summary for every field'), and the description delivers the entire nested contract: defaults, enums, ranges, cardinality limits, and 'primary' semantics. This adds substantial meaning the schema does not encode.

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 pair (register/update) plus the exact resource (game manifest of an app family you author) and even scopes it as 'API only, no republish', which cleanly separates it from the publish_app sibling. An agent can identify this tool without opening any schema.

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?

Gives clear context ('API only, no republish') and states the authoring precondition plus full auth requirements, which implies publish_app is the alternative for republishing. It never names that alternative explicitly, so it stops one step short of a 5.

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