report_create

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only mentions 'requires confirm=true,' a detail already present in the schema. It does not describe cost, asynchronous behavior, effects on the notebook, or what the generated report looks like.

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 a single sentence with no filler and is easy to parse. However, it is so brief that it sacrifices valuable guidance, so it does not earn a 5.

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?

This is a six-parameter tool with no output schema and no annotations, yet the description only says 'Generate a text report (requires confirm=true)'. Missing context around report_format options, source_ids behavior, custom_prompt usage, and result handling leaves it incomplete for an agent deciding to invoke it.

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 adds no new parameter semantics beyond what the schema already documents; 'requires confirm=true' merely restates the confirm parameter's existing description.

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 generates a text report, using a specific verb and resource. It distinguishes from sibling content-creation tools like audio_overview_create or slide_deck_create by specifying 'text report', though it does not elaborate on what that entails.

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?

There is no guidance on when to use report_create versus sibling tools such as quiz_create, slide_deck_create, or infographic_create. The only implication is that it is appropriate when a text report is desired, but no explicit context, prerequisites, or exclusions are provided.

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