create_report

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

The description only states that it creates a report. With no annotations, it bears full responsibility for behavioral disclosure. It fails to mention side effects, permissions required, or any constraints, which is insufficient 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?

While the description is short, it is under-specified rather than concise. It does not earn its place because it omits critical information that an agent needs, such as parameter details or behavioral context.

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 absence of output schema, full parameter dependency on an undocumented object, and no annotations, the description is grossly incomplete. It does not answer basic questions about what the tool returns or how to use the single parameter effectively.

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 one required parameter 'report_data' of type object with no defined properties (0% schema description coverage). The description adds no meaning about the content or structure of this object, leaving the agent without guidance on how to populate it.

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 new report in OpenMetadata' clearly identifies the verb and resource, distinguishing it from other create tools targeting different entities. However, it lacks specificity about what constitutes a 'report' in OpenMetadata, which would help an agent differentiate among similar create 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 usage guidelines are provided. There is no indication of when to use this tool versus alternatives like update_report, or any prerequisites (e.g., existing data). The agent receives no context for appropriate invocation.

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