create_report

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

With no annotations, the description adds useful behavioral context: reports are scoped to YOUR profile, cron scheduling is optional, and docsConsulted must be true. However, it does not disclose whether authentication is required, what side effects occur on duplicate names, or what the response contains.

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 purpose is front-loaded and the remaining sentences quickly cover scheduling, the docs gate, and the documentation-first rule. 'or a dashboard definition' is slightly tangential for a report-creation tool, but overall the description is compact and scannable.

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?

The schema plus description give enough to invoke the tool with the required name, search, and docsConsulted fields. But there is no output schema and no mention of authentication or return behavior, so the description is not fully complete for a 9-parameter write operation.

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 detailed property descriptions already carry most of the parameter meaning. The description only restates the cron option and the docsConsulted requirement without adding new semantics for the other parameters.

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 verb and resource: 'Create a report (saved search) under YOUR profile.' The parenthetical 'saved search' and the personal profile scope clearly distinguish it from sibling tools such as create_dashboard and create_alert.

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?

It mandates a docs-first workflow and the docsConsulted=true gate, but it never names alternatives or states when not to use this tool. The intended use is implied by the tool name and 'report (saved search)' rather than explicitly contrasted with create_alert or create_dashboard.

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