sigma_create_report

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

The description adds no behavioral context beyond the annotations. Annotations indicate the tool is not read-only and not destructive, but the description doesn't disclose side effects, return values, or any requirements. It fails to leverage the opportunity to explain what 'create a report' actually entails.

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 words is extremely concise, but this is under-specification rather than effective conciseness. The single sentence does not earn its place because it conveys almost no useful information for tool selection or invocation.

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?

For a tool with a complex, undocumented 'body' object and an output schema, this description is completely inadequate. There are no examples, no prerequisites, no description of the report object structure, and no differentiation from sibling tools. The agent cannot confidently invoke this 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?

The input schema has a single 'body' parameter with an arbitrary object (additionalProperties true) and 0% schema description coverage. The description 'Create a report.' provides no information about what fields are expected in 'body', so the agent is left completely unguided about parameter semantics.

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 a report.' clearly states the action (create) and resource (report). It is not a tautology, but it does not distinguish this from sibling tools like sigma_create_workbook or sigma_convert_workbook_to_report, which are also creation operations.

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 given about when to use this tool, prerequisites, or alternatives. The description is too brief to convey any usage context, leaving the agent without information on how this differs from other report-related tools.

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