get_introduction_section_prompt

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

No annotations exist, so description carries full burden. It states the tool covers disease burden, treatment landscape, study rationale, objective statement, AMA style, and explicitly notes 'No references included'. This provides key behavioral context, though it does not clarify that the output is a prompt (rather than a drafted section).

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 very concise (5 lines) with front-loaded main action. Every sentence adds value: purpose, content coverage, style, and an exclusion note. No superfluous words.

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 4 parameters (3 required), output schema present, and siblings indicating a family of prompt generators, the description covers core intent and style but lacks parameter explanations and usage context, making it minimally 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 description coverage is 0% and the description gives no information about the 4 parameters (drug_or_topic, indication, target_journal, word_length). The description must compensate for the lack of schema descriptions but does not, leaving the agent with no parameter guidance.

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?

Clearly states the verb 'Draft' and resource 'manuscript Introduction/Background section'. The description distinguishes from siblings like get_discussion_section_prompt by specifying content coverage (disease burden, treatment landscape, etc.) and style (AMA, no references).

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?

Usage is implied by the name and context (sibling tools are all section prompts), but there is no explicit guidance on when to use vs. alternatives, nor any exclusion criteria or prerequisites.

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