create_report

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states 'create,' implying a write operation, but does not mention permissions, side effects, resource limits, or what happens to existing data. The lack of any behavioral detail is a significant gap for a mutation tool.

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 only two words, which is too brief to be effectively front-loaded. While concise, it sacrifices useful content; important details about the tool's function and parameters are missing, making it under-specified.

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?

Given the tool has 6 parameters, 3 required, and no output schema, the description is severely incomplete. It fails to explain return values, error conditions, or any side effects. The minimal text does not provide enough information for an AI agent to use the tool correctly.

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 basic descriptions for all 6 parameters. The description does not add meaning beyond the schema. As per guidelines, baseline is 3 when coverage is high, and no extra value is provided here.

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 'Create custom report' indicates the general action (create) and resource (report) but lacks specificity to distinguish it from other 'create' sibling tools like create_campaign or create_contact. It does not clarify what constitutes a custom report or how it differs from a standard report.

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?

No guidance is provided on when to use this tool versus alternatives. There are many create tools in the sibling list, but the description offers no context, prerequisites, or exclusions to help the agent decide.

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