get_pub_plan_executive_summary_prompt

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

Discloses output length (~300-350 words) and key content areas (strategic rationale, data assets, etc.), but no details on side effects, authorization, or potential limitations. Without annotations, the description provides minimal behavioral context.

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?

Single sentence with bullet-like details, efficiently conveying purpose and scope. Front-loaded with a tag, but could include parameter guidance without significant bloat.

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?

While output schema exists and reduces the need to describe return values, the tool has six required parameters with zero description. The description does not address parameter usage or constraints, making it incomplete for effective invocation.

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 information about the six required parameters (drug, indication, audience, etc.). The description fails to compensate for the lack of schema descriptions, leaving the agent to infer parameter meaning from names alone.

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 tool 'Write a one-page publication plan executive summary for medical affairs leadership,' specifying the resource (executive summary) and audience. Distinguishes from siblings like get_publication_plan_framework_prompt by targeting a specific, high-level output.

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?

Target audience 'for medical affairs leadership' implies context, but no explicit guidance on when to use this tool vs. other prompt generators. No alternatives or prerequisites mentioned.

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