createSurveyResultsSlide

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

With no annotations, the description must disclose behavioral traits. It only says 'Create or update', implying a mutation, but does not state side effects, permission requirements, or how the tool interacts with existing slides. The brevity leaves significant uncertainty about the tool's behavior.

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 a single sentence with no redundancy, which is concise. However, it is too terse to be informative; conciseness should not come at the cost of clarity. It earns a middle score due to efficient wording but insufficient substance.

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 the tool has 3 parameters (1 required), no output schema, and complex purpose (creating/updating slide content), the description is incomplete. It does not explain the return value, the relationship between questions and summaries, or how the tool fits into a larger presentation workflow. Critical information is missing.

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?

The schema description coverage is 33% (only _index has a description). The tool description does not explain the 'questions' and 'summaries' parameters, which are undocumented in the schema. The description adds no value beyond the schema for these parameters, and the low coverage is not compensated.

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 states the tool creates or updates a 'survey results summary', which is a specific resource. The verb is clear, and it distinguishes from sibling tools like 'createSwotSlide' by focusing on survey results. However, it lacks explicit differentiation from other slide creation tools, but the name provides enough context.

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?

No guidance is given on when to use this tool versus any of the many sibling slide creation tools. The description does not explain scenarios for creating vs updating, nor does it mention prerequisites or post-conditions.

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