client_onboarding_checklist

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

No annotations provided, so description carries full burden. It discloses an important cost behavior: 'Does not count against your monthly draft limit.' This is a valuable behavioral trait beyond the standard generative function. No contradictions with annotations since none exist.

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?

Four sentences, each serving a distinct purpose: what it does, how it adapts, when to use, and a behavioral note. No wasted words, front-loaded with core function. Excellent structure.

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?

Covers main function, adaptation, and timing, but lacks details on output format (e.g., bulleted list, plain text) and edge cases. Given no output schema, a brief format hint would improve completeness for an agent to expect the response type.

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 coverage is 100% with descriptions for all 4 parameters. The description reinforces that the checklist adapts by project_type and is tailored, but adds no new constraints or format details beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states the verb 'Generate' and the resource 'tailored list of everything you need from a client', specifying it adapts by project type. This distinguishes it from sibling tools that send emails or proposals, as it focuses on creating an actionable checklist for client onboarding.

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?

Explicit instruction: 'Send this after the kickoff email, before starting work.' This provides clear context for when to use the tool, but does not mention specific alternatives or when not to use it, which would elevate it to a 5.

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