openpanel_delete_client

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

Lacks annotations and fails to disclose critical behavioral details: whether deletion is permanent, if it invalidates active tokens, or required authorization levels. Only implies destruction via the verb 'Delete' without consequence warnings.

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?

Single sentence is appropriately brief, but the '[UNIFIED]' tag appears to be internal metadata leakage that doesn't serve the agent, slightly undermining the value of the sentence.

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?

Inadequate for a destructive operation with three undocumented parameters. No output schema, no warnings about irreversibility, and no explanation of what constitutes an 'API client' in this context.

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?

With 0% schema description coverage, the description compensates minimally by identifying the resource type (API client), hinting at client_id's purpose, but provides no semantics for 'site' or 'project_id' parameters.

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?

Clearly states the action (Delete) and resource (API client). While the '[UNIFIED]' prefix is unexplained metadata noise, the core purpose is unambiguous from the verb-object pair.

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?

Provides no guidance on when to use this tool versus sibling operations like oauth_revoke_client or openpanel_regenerate_client_secret, and lists no prerequisites (e.g., required permissions).

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