get_revised_manuscript_cover_letter_prompt

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

No annotations provided, so description carries full burden. It discloses tone and word count but does not clarify if the output is a drafted letter or a prompt (ambiguous given tool name includes 'prompt'). Missing details on behavior like input validation or rate limits.

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?

Two sentences with no unnecessary words. Purpose and key details are 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?

Description lacks clarity on output nature (prompt vs. letter) and fails to cover parameter semantics. Given a moderately complex tool with 4 required inputs, more detail is needed for completeness.

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 provides no explanation of the four parameters (journal, manuscript_title, manuscript_number, major_revisions). The agent gets no guidance on required inputs 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 the tool drafts a cover letter for a revised manuscript, specifies tone (professional, confident, collegial) and length (~200-250 words). It distinguishes from siblings like 'get_author_revision_response_prompt' which is for response letters.

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 implies usage for revised manuscript submissions but does not explicitly state when not to use or mention alternatives among sibling tools. No guidance on selecting this tool over others.

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