create_report

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

Annotations indicate this tool is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds the permission requirement ('WRITE_ENABLED=true'), which is useful. No contradiction with annotations. The description does not elaborate on side effects or idempotency, but the openWorldHint=true suggests the tool may have side effects outside the system, which is acceptable.

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 that communicates the purpose and a key requirement. It is front-loaded and contains no extraneous words.

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?

While the description is clear, it lacks information about the return value (e.g., the created report's ID) and does not explain complex parameters like 'query' or 'field'. Given the tool has 8 parameters and no output schema, a bit more context would be helpful, but the schema descriptions partially compensate.

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 field descriptions already document all 8 parameters. The description adds minimal additional meaning beyond restating the 'table' parameter ('on any table'). With high coverage, a baseline of 3 is appropriate.

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 action ('Create'), the resource ('a new saved report'), and the scope ('on any table'). It distinguishes from sibling tools like 'create_scheduled_report' and 'get_report' by specifying 'saved report' and the WRITE_ENABLED requirement.

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?

The description mentions a prerequisite ('requires WRITE_ENABLED=true'), which helps the agent decide when to use this tool. However, it does not explicitly mention when to use alternatives such as 'update_report' or 'create_scheduled_report', leaving some ambiguity.

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