game_center_matchmaking_teams_delete_instance

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

No annotations are provided, so the description carries the full burden. The literal DELETE route implies a destructive mutation, but the description does not disclose whether deletion is permanent, whether dependent rule-set associations cascade or block the delete, or what permissions are required — all critical for an irreversible operation.

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 whole content is one route string duplicated inside parentheses, so half the text is pure redundancy with zero information gain. What remains is not front-loaded prose but a raw path.

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 destructive tool with no annotations and no output schema, the description should at minimum state permanence and side effects. It provides nothing beyond the endpoint path, leaving an agent unable to reason about consequences of the 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% and the single 'id' parameter is documented in the schema as 'the id of the requested resource'. The description adds no additional meaning such as format or where to obtain the id, but the schema does the necessary work, so baseline 3 applies.

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 is only the HTTP route 'DELETE /v1/gameCenterMatchmakingTeams/{id}' repeated verbatim in a parenthetical. It does convey the verb (delete) and resource (matchmaking team) via the URL, but it is essentially a restatement of the tool name rather than a stated purpose, and it gives no plain-language framing of what a 'matchmaking team' entity is.

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 siblings like game_center_matchmaking_teams_update_instance or game_center_matchmaking_teams_create_instance, nor any prerequisites such as needing to remove a team from a rule set first. The agent is left to infer everything from the route.

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