delete_user

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

No annotations are provided, so the description must disclose side effects. It only states the deletion action and that a JSON object is returned; it does not mention permanence, required permissions, cascading effects, or reversibility—critical for a destructive 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?

The description is compact and well-structured with a clear purpose, Args, Returns, and an Example. Every line adds value, and the format makes it easy to parse.

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 simple deletion tool with an output schema (per context signals), the description is mostly adequate. However, it lacks warnings about destructive consequences or prerequisites, which are important 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?

The schema provides only a type and title for user_id, but the description's Args section explains 'The user ID to delete,' adding necessary semantic meaning. The parameter is simple and sufficiently documented.

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 opens with 'Delete a user from AgencyAnalytics,' clearly specifying the action and resource. It distinguishes from sibling tools like create_user, update_user, list_users, and get_user.

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?

Clear context for use: you call this to delete a user. However, it does not provide explicit exclusionary guidance or mention alternative approaches (e.g., deactivation via update_user), though the purpose is unambiguous.

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