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

No annotations are provided, so the description carries the full behavioral disclosure burden. It adds useful context: the primary-profile restriction and the requirement to authenticate with a Proof account rather than relying on start_login. Still, it doesn't disclose irreversibility, side effects, or what a successful/failed deletion returns.

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: core action first, constraint second, access instructions last. Each sentence adds a distinct piece of information without unnecessary padding.

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 one-parameter destructive tool, the key constraint and authentication requirement are covered. However, with no output schema and no annotation coverage, the description leaves the deletion's permanence, side effects, and expected return behavior to inference.

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?

There is only one parameter, profile_id, and the schema already describes it as 'Profile ID' with 100% coverage. The description adds no additional parameter meaning beyond saying deletion is by ID, so the baseline score of 3 applies.

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?

States a specific verb ('Delete'), resource ('profile'), and lookup key ('by ID'). It is clear and unambiguous, though it doesn't explicitly differentiate itself from sibling deletion tools like delete_profile_template.

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 the tool is used when a profile needs to be deleted and gives one important exclusion (cannot delete the primary profile if it is the only one). However, it does not name alternatives or provide explicit when-to-use versus when-not-to-use guidance beyond that constraint.

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