Generate cite keys

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description need only add context — and it does: repeated keys get a letter suffix, and the response contains the old/new key pair per entry plus a full BibTeX list. It doesn't mention any rate limits or failure modes for unparseable input, keeping it short of a 5.

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?

Front-loaded with the rule, then collision handling, then return contents — a sensible order. The trailing example restates the smith2024deep pattern already given and is longer than strictly necessary, so it loses a point for redundancy rather than length.

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?

An output schema exists, so return values needn't be spelled out, yet the description covers the old/new key mapping and BibTeX output anyway. The only gap is guidance on which input formats are accepted beyond the schema's enum and what happens with malformed text, but for a 3-param read-only tool this is close to complete.

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 goes beyond the schema by demonstrating include_title_word's effect concretely (smith2024deep vs smith2024) and by implying format detection behavior, though it never discusses the format parameter's auto/bibtex/ris/csl_json choices.

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?

States a specific verb+resource (create cite keys) plus the exact derivation rule (first author's family name, year, first meaningful title word) and the collision behavior. Nothing about parse_bibliography, convert_bibliography, dedupe_entries or lint_entries overlaps with this key-generation transformation, so the agent can distinguish it immediately.

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 makes clear what the tool produces but never says when to choose it over siblings such as convert_bibliography or dedupe_entries, nor does it state prerequisites (e.g. the text must already be parsed/unambiguous). Usage is only implied by the nature of the operation.

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