delete_profile

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the deletion action, the primary-profile edge case, and the Proof-account/API-key requirement, which is useful context. However, it does not disclose whether deletion is permanent, what cascading effects occur, or what response the caller should expect.

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 front-loaded: the core purpose appears in the first sentence, while the second section adds necessary access and constraint details. Every sentence earns its place with no filler or repetition.

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 one-parameter delete tool with no output schema, the description covers the key preconditions: Proof account, API key setup, restart requirement, and the notable limitation about deleting a sole primary profile. It could mention response/return behavior, but the essential information for selecting and invoking the tool correctly is present.

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 has 100% coverage for the single parameter, describing profile_id as 'Profile ID.' The description adds only 'by ID,' which does not meaningfully extend the schema's parameter semantics. A baseline of 3 is appropriate because the schema already documents the parameter adequately.

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 states a specific verb and resource: 'Delete a profile by ID.' The constraint about the primary profile further distinguishes it from profile mutation tools like update_profile or set_primary_profile. There is no ambiguity about the operation being performed.

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 gives an implied usage context and a clear operational prerequisite, but it does not explicitly state when to prefer this tool over alternatives or mention sibling tools such as update_profile. It does provide a negative routing signal with 'start_login does NOT open this tool,' which helps avoid incorrect invocation.

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