game_center_matchmaking_rule_sets_update_instance

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

With no annotations, the description carries the full behavioral burden, yet it only implies partial-update semantics via the PATCH method. It says nothing about permissions, whether omitted fields are preserved, reversibility, or side effects on queues/rules that reference the rule set.

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 endpoint string is duplicated verbatim inside parentheses ('PATCH /v1/... (PATCH /v1/...)'), which is pure waste, and the whole description is a pointer to an external schema rather than a self-contained statement.

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 mutation tool with no annotations, a nested JSON:API body, and no output schema, the description should explain the update contract. Instead it defers entirely to an external OpenAPI component, leaving the agent without the information needed to construct a correct call.

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 100%, so the baseline is 3. The description references the body's OpenAPI component but adds no field-level meaning (e.g., which attributes are updatable, required envelope keys) beyond what the schema already states.

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 conveys an update operation only through the raw REST path 'PATCH /v1/gameCenterMatchmakingRuleSets/{id}', never stating in plain language what is being modified. It does distinguish itself from sibling get/delete/create variants via the PATCH verb, but the agent must parse a URL to infer purpose.

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 guidance on when to use this tool versus create_instance, delete_instance, or get_instance for the same rule set, nor any prerequisite or context. The agent is left to infer usage entirely from the name and path.

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