game_center_leaderboards_v2_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 of behavioral disclosure, and it discloses nothing. It does not say whether the delete is destructive or reversible, what permissions are required, whether cascading effects occur, or what a successful response looks like for this mutation.

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?

It is short, but not concise in a useful sense: the identical path string is repeated verbatim inside parentheses, which is pure redundancy rather than front-loaded information. The single content-bearing sentence is effectively a restatement of the tool name.

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?

This is a destructive mutation with no annotations, no output schema, and only a raw path as a description. An agent has no information about irreversibility, required scopes, or side effects, so the definition is wholly inadequate for the operation it exposes.

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?

There is a single parameter ('id') and schema description coverage is 100%, so the schema already defines it as 'the id of the requested resource'. Per the baseline rule for high coverage, a 3 is appropriate since the description adds no additional meaning about the identifier's format or source.

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 just the raw HTTP verb and path, 'DELETE /v2/gameCenterLeaderboards/{id}', duplicated in parentheses. It conveys a delete operation on the leaderboards resource only via URL convention, but adds nothing beyond what the tool name already states, and does not distinguish it from siblings like game_center_leaderboards_delete_instance or game_center_leaderboard_sets_v2_delete_instance.

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?

No when-to-use, prerequisites, or alternative-tool guidance is present. The agent receives no context on when this V2 delete should be chosen over the V1 variant or any of the many other delete tools in the sibling list.

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