payments_delete_profile

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

With no annotations provided, the description must disclose all behavioral traits. It only states it deletes a profile and requires confirmation, but omits critical details such as whether deletion is permanent, cascading effects, permissions needed, or error scenarios. This is insufficient for safe invocation.

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 very concise with two short sentences, immediately stating the core action and a crucial user requirement. Every word earns its place; no redundancy.

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 no output schema and no annotations, the description is too sparse. It lacks information on return values, error handling, prerequisites (e.g., customer existence), or lifecycle implications (e.g., irreversible removal). The tool's simplicity does not excuse the omission of behavior beyond deletion.

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 coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema descriptions ('Customer ID', 'Profile ID', 'Must be true') by reiterating the confirmation requirement. It does not clarify format, constraints, or relations between 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?

The description clearly states the verb 'Delete' and resource 'a payment profile,' distinguishing it from sibling tools like payments_create_profile or payments_update_profile. The addition 'The user MUST confirm' emphasizes a critical precondition, making the purpose unambiguous.

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 implies usage through the name and the requirement for confirmation, but it does not explicitly state when to use this tool versus alternatives like payments_update_profile. However, the clear verb-resource pairing and the sibling list provide adequate context for an AI agent to infer appropriate usage.

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