lc_preview_rekey_extension

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

No annotations exist, and the description only says 'Preview rotating', which implies a dry-run, but it does not explicitly state whether the operation is read-only or has side effects. The parameter token_ttl_seconds suggests configuration, but no behavior is disclosed.

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 one sentence, no wasted words, but it lacks structure or additional context. It is concise but could benefit from slightly more detail without losing brevity.

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?

With no output schema, no annotations, and 0% parameter coverage, the description is severely incomplete. It does not explain what the preview returns, prerequisites, or how to use the parameters, leaving an AI agent with insufficient information.

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 0%, and the description adds no explanation for any of the three parameters (oid, extension_name, token_ttl_seconds). The meaning of oid and the purpose of token_ttl_seconds are entirely unspecified.

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 'Preview rotating an extension subscription API key' clearly defines the action (preview rotate) and resource (extension subscription API key), distinguishing it from sibling preview tools like lc_preview_subscribe_extension or lc_preview_update_extension.

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?

No guidance on when to use this tool versus alternatives, such as lc_preview_update_extension or lc_preview_subscribe_extension. No prerequisites or context are provided, making it unclear if certain conditions must be met.

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