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

With no annotations provided, the description carries the full burden. It discloses irreversibility ('This action is irreversible') and the return value ('Returns the deleted template id and a deleted flag'), which are key behavioral traits. It also implies the operation is scoped to a connected Clerk application. No contradictions with annotations exist.

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 four sentences, each adding value: purpose, prerequisite, irreversibility/return, and cost. It is front-loaded and contains no fluff or 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?

For a two-parameter delete tool with no annotations and an output schema, the description covers all necessary context: what it does, how to select the target, irreversibility, and the expected return. It does not need to explain error handling or return format further, as the output schema exists.

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 adds a bit of usage context for clerk_instance_id ('target a specific connection, or omit it to use the default account'), but this largely mirrors the schema description. No significant additional meaning is provided for template_id beyond the schema's mention of retrieve/update/delete.

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 ('Permanently delete') and resource ('JWT template'), clearly distinguishing it from sibling tools like update_jwt_template or create_jwt_template. The 'permanently' qualifier adds important scope beyond a generic delete.

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?

Provides clear prerequisite guidance ('Call clerk.get_connected_accounts first') and clarifies how to target a connection (pass clerk_instance_id or omit for default). It does not explicitly mention alternatives or state when not to use this tool, but the context is sufficient for an agent to invoke it correctly.

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