x_api_delete_lists

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly states the tool is mutating and high-risk, lists required OAuth scopes, explains environment-selection behavior, gives an expected response shape, and lists common failure conditions. This is comprehensive transparency.

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 description is well-structured with labeled sections (Risk, Required permissions, Parameter formats, Expected response, etc.). It is lengthy but informative, with only clear redundancy being 'Use when: Delete List' repeated after the initial 'Delete List.' Overall, the structure helps scanning, though it could be tightened.

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?

Given the tool's complexity (7 parameters, no annotations, no output schema), the description is remarkably complete: it covers auth prerequisites, selection of credentials, failure modes, response shape, safety warnings, and an example. The main gap is the lack of detailed semantics for all parameters, particularly authorizationKey and preferredAuthType, which prevents full self-contained operation.

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 description adds meaning for several parameters: it explains that scopeTenantId plus scopeUserId or scopeAccountId selects the auth tenant principal, and credentialKey selects a non-default credential profile. It also mentions id as required path parameter. However, with 0% schema coverage, two parameters (authorizationKey, preferredAuthType) are not explained, and the description says id's format is 'unknown' rather than providing useful details like 'the ID of the list to delete.'

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 begins with 'Delete List,' which is a specific verb+resource that clearly states the tool's function. This distinguishes it from siblings like x_api_create_lists, x_api_get_lists_by_id, and x_api_update_lists.

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 description provides a 'Do not use when' section that explicitly tells the agent to prefer x_schema_discovery or x_query_suggestion for exploration, and to use auth/configuration tools when needed. It also lists recommended prerequisite and follow-up tools. However, the 'Use when' clause merely restates the tool's purpose ('Delete List') and lacks specific conditions or context for when deletion is appropriate.

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