create_report

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

No annotations provided, but description discloses authentication requirement (API key) and return value (session_id for subsequent calls). Could mention side effects or error handling but adequate.

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 plus an example, front-loaded with main action. No wasted words, efficient 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 purpose, usage restrictions, prerequisites, and return value. With output schema but no annotations, description is sufficient for invocation. Lacks error handling details.

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?

Only one parameter 'description' with 0% schema coverage. Description adds meaning by specifying 'natural language description' and providing an example, though lacks format or length constraints.

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?

Clear verb ('create') and resource ('Power BI report') with method ('from a natural language description'). Example distinguishes it from siblings like create_dashboard.

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?

Explicitly states when NOT to use (when user provides CSV/dataset file path) and directs to create_dashboard. Also mentions prerequisite (valid Anthropic API key).

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