app_asset_library_placements_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 behavioral burden, yet it discloses nothing beyond the verb embedded in the URL. It does not state that the operation is destructive/irreversible, whether it requires specific permissions or a placement ordering step, whether it is idempotent, or what happens on missing/invalid IDs.

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 text is short but this is under-specification rather than conciseness. It also redundantly repeats the identical endpoint string twice inside the parentheses, which is pure noise.

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 single-parameter tool with no annotations and no output schema, the description should at least confirm the deletion target and irreversibility. It provides only a raw endpoint string, leaving the agent with no context beyond what the tool name already encodes.

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% for the single 'id' parameter, so the schema already documents it. The description adds no format, source, or constraint information beyond the path placeholder. The baseline of 3 applies when the schema does the heavy lifting and the description contributes nothing extra.

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 nothing but the HTTP endpoint path repeated verbatim in parentheses: 'DELETE /v1/appAssetLibraryPlacements/{id}'. It conveys the verb and resource implicitly through the URL, but adds no plain-language statement of what is being deleted or its effect, and does not distinguish this tool from siblings such as app_asset_library_placements_get_instance or app_asset_library_placements_create_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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is left to infer that this destroys a placement solely from the word DELETE in the path.

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