get_speaker_notes_prompt

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

Without annotations, the description includes important behavioral constraints like 'Describe data in general terms' and 'Do not paste unpublished figures'. This adds safety context, though it could further disclose output characteristics.

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 concise, front-loaded with purpose, and contains no redundant information. Every sentence serves a purpose.

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?

The description covers purpose and safety but lacks usage guidelines and parameter details. Given the existence of an output schema, return value explanation is less critical, but completeness could be improved.

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 does not explain the parameters. While parameter names are self-explanatory, the description should add meaning beyond the schema, which it fails to do.

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 writes speaker notes for data slides and specifies the content goals (contextualize data, explain graph, highlight clinical meaning, address questions). This distinguishes it from sibling tools that generate other types of content.

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 data slides but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusion criteria or mention related tools.

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