case_study_outline

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

No annotations are provided, so the description carries full burden. It mentions the draft limit exemption but fails to disclose whether the tool is read-only or has other side effects, authentication needs, or rate limits.

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 two concise sentences plus a single note. It is front-loaded with the core action and adds valuable context about output format and draft limits without any wasted 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?

For a tool with 7 parameters, no output schema, and moderate complexity, the description provides sufficient context about the output (challenge, approach, results, learnings) and the target user (freelancers). It is complete enough for the intended use case.

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 100%, so the baseline is 3. The description lists outline sections like 'learnings' that are not parameters, adding slight context but not enhancing understanding of the actual parameters beyond what the schema already provides.

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 transforms a completed project into a structured portfolio case study with specific outlined sections. It distinctly differentiates itself from the sibling tools, which are primarily email templates and proposal-related, by focusing on portfolio documentation.

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 explicitly states the tool is for turning completed projects into case studies, noting it 'does not count against your monthly draft limit.' While it doesn't provide negative guidance or alternatives, the sibling context makes the use case clear.

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