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

Goes beyond annotations by explaining the resolution precedence and the important warning that omitting both options never creates a blank report. The only minor gap is the lack of an explicit precedence statement when both template_id and blank:true are supplied together.

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?

Three sentences, no filler, and the key behavior is front-loaded. Every sentence earns its place by adding resolution logic or practical guidance.

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 composite creation tool, the description covers the decision branches, warns against unintended blank reports, and points to the right template search path. With an output schema present, return details are not required; only the combined-option ambiguity keeps this from being fully complete.

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%, so the baseline is 3; the description adds meaningful semantics for template_id, blank, and type, including the list_templates filtering hint. It does not add new meaning for name/report_name/website/timezone, but those are already described in the schema.

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 a specific action and resources: 'Create a new client and its first report or dashboard in one step.' It clearly differentiates from siblings like create_client and create_report by emphasizing the one-step combined behavior.

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?

Provides clear conditional guidance: use template_id to clone, blank:true for empty, and neither to clone a matching Starter template. It also directs users to list_templates for specific styles. However, it does not explicitly state when to prefer separate create_client/create_report calls instead.

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