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

With no annotations, the description bears the burden of behavioral disclosure. It communicates read-only intent ('Retrieve'), explains the default account behavior when clerk_instance_id is omitted, and lists the returned fields. It also adds the prerequisite call and token cost. This goes beyond the schema, though it does not discuss potential errors or permissions.

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 serving a distinct purpose: purpose, prerequisite/usage, return fields, and cost. No superfluous information, and the key information is front-loaded.

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?

The tool has only 2 parameters and an output schema, so the description needn't explain return values in depth. It adequately covers prerequisites, parameter selection, and return fields. The main gap is the lack of comparative guidance against list_jwt_templates, but overall it is sufficiently complete for a simple retrieval tool.

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 description coverage is 100%, so the schema already documents both parameters. The description adds marginal value by reinforcing clerk_instance_id's default behavior and the need to call get_connected_accounts first, but it does not introduce new parameter details beyond the schema.

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 'Retrieve a single JWT template from a connected Clerk application.' The verb 'Retrieve' and the resource 'JWT template' are specific, and the word 'single' differentiates it from list_jwt_templates and mutations like create/update/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 explicit prerequisites ('Call clerk.get_connected_accounts first') and clarifies how to target a specific connection with clerk_instance_id versus omitting it for the default. However, it does not explicitly mention when to use this tool over list_jwt_templates or when not to use it, so it lacks exclusions/alternative guidance.

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