end_user_license_agreements_delete_instance

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

With no annotations, the description must carry the behavioral burden. 'DELETE' implies a destructive operation, but it says nothing about permanence, cascading effects, required permissions, or whether the EULA can be recovered or recreated.

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 the parenthetical repeats the path verbatim, so the one sentence is redundant rather than informative. The content is under-specified, not concise.

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 mutation endpoint with no annotations and no output schema, the description is missing almost everything an agent needs: confirmation of destructive semantics, side effects, and permission requirements.

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?

The single 'id' parameter is fully documented in the schema ('the id of the requested resource'), so the baseline is 3. The description adds no extra meaning such as whether the id is an app's EULA relationship id or a resource id.

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 only restates the endpoint path, duplicating the tool name's verb and resource ('DELETE ... endUserLicenseAgreements'). It adds no scope or distinction from the many sibling delete_instance tools.

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 indication of when to use this tool versus get_instance, update_instance, or other delete endpoints. No prerequisites or cautions are mentioned.

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