case_study_generator

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

No annotations are provided, so the description carries the full burden. It discloses the major output components (Challenge-Solution-Results, quotes, metrics, one-pager, social snippets), but does not surface caveats like output format or how optional inputs are handled.

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, front-loaded sentence with no filler. Every phrase adds value, efficiently conveying the tool's purpose and deliverables.

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 adequately explains the tool's purpose and output components, but because there is no output schema, it lacks specifics about return format or how the one-pager and social snippets are delivered. This is sufficient for selection but not full invocation confidence.

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 input schema has 100% description coverage for all 8 parameters, so the baseline is 3. The description adds no parameter-specific detail beyond mentioning quotes and metrics, which the schema already covers.

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 'Generate complete B2B case study' with explicit structure (Challenge-Solution-Results), including customer quotes, metrics, one-pager, and social snippets. This is a specific verb+resource and clearly differentiates from siblings like newsletter_builder or webinar_script.

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 the tool is for creating B2B case studies, giving clear context for when to use it. However, it does not provide explicit when-not-to-use guidance or mention alternatives such as testimonial_capture or content_repurposer.

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