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

With no annotations, the description carries the full burden. It discloses the return behavior ('summary without the secret') and cost ('Cost = 3 tokens'), but does not explicitly state read-only safety, auth needs, or error conditions. The verb 'Retrieve' implies read-only, but more explicit disclosure would strengthen this.

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 five short, front-loaded sentences. Every sentence earns its place: purpose, prerequisite, parameter guidance, return behavior, and cost. 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?

Given the tool's simplicity and the presence of an output schema (which explains return values), the description covers essential context: purpose, usage prerequisite, parameter default, and cost. It lacks mention of error handling or rate limits, but those are not critical for a simple read with an output schema.

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 baseline is 3. The description adds meaning by explaining clerk_instance_id's default behavior ('omit it to use the default account') and the prerequisite get_connected_accounts, which enriches the schema definition. api_key_id is not elaborated, but schema already covers it.

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 API key metadata by id from a connected Clerk application' with a specific verb and resource. It distinguishes itself from siblings like get_api_key_secret by explicitly noting 'without the secret' and from list_api_keys by focusing on a specific id.

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: 'Call clerk.get_connected_accounts first' and explains how to target a connection via clerk_instance_id or use the default account. Does not explicitly mention when to use alternatives (e.g., get_api_key_secret for secrets), but the context is strong.

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