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

With no annotations, the description carries the burden of exposing behavior and does so by stating the destructive effect, the fallback to the default template, and the authentication prerequisite. It could add whether the deletion is permanent or how errors are surfaced, but the core behavior is transparent.

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 two short paragraphs with the core behavior first and the access warning second. Every sentence adds information, and there is no filler or repetition of the tool name.

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 three-parameter delete tool with no output schema, the description covers what happens, the required authentication, and a common failure path (unauthenticated use). It is slightly incomplete in not spelling out that profile_id selects the profile whose custom template is deleted, but the overall context is sufficient.

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 the baseline is 3; the description does not add detail about profile_id beyond the schema. The prose 'channel and message type' mirrors the channel and type fields, and profile_id is left generic while it plausibly refers to the profile whose template is being removed.

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 action (Delete) on a specific resource (custom profile template) and describes the consequence: reverting to the default template for the given channel and message type. The qualifier 'custom' distinguishes it from sibling tools like delete_template and delete_profile without relying on the name alone.

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 practical invocation guidance: a Proof account is required, the client must be authenticated, and start_login does not make this tool reachable. However, it does not explicitly say when to choose this over update_profile_template or delete_template, nor does it state conditions under which it should not be used.

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