app_store_version_submissions_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 disclosure burden. Apart from flagging deprecation, it says nothing about reversibility, required permissions, side effects on the related app store version, or error behavior — significant gaps for a destructive delete 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?

It is short and front-loads the deprecation marker, which is good. But the route is duplicated verbatim in parentheses, which is pure redundancy and the only real content the description carries.

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 deprecated destructive endpoint with no annotations and no output schema, an agent still needs to know the replacement path, side effects, and permission requirements. None of that is present, leaving the definition inadequate for safe invocation.

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 one parameter with 100% schema description coverage, so the schema already documents it. The description adds nothing beyond echoing the {id} path placeholder, matching the baseline 3 for high-coverage schemas.

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 the HTTP verb (DELETE) and the resource path (appStoreVersionSubmissions/{id}), so the operation is identifiable. However, it is essentially the tool name and route restated, with no plain-language statement of what a submission is or what deleting it accomplishes, and no differentiation from the many other delete_instance siblings.

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?

The [DEPRECATED] tag hints that the tool should be avoided, but the description never says what to use instead, nor under what conditions deletion is appropriate or permitted. No when-to-use or when-not-to-use guidance is offered.

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