list_reports

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

No annotations are provided, so the description must carry full burden. It only states 'List reports' as a read operation and mentions pagination/filtering. It does not disclose defaults (e.g., include_deleted=false), authentication requirements, rate limits, or any side effects. Significant behavioral gaps remain.

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?

Description is a single sentence front-loading the purpose, which is efficient. However, it is too brief and omits critical details, making it under-specified. It earns its place but sacrifices completeness for brevity.

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?

With 5 parameters, no output schema, and no annotations, the description is inadequate. It does not explain return format, pagination behavior (e.g., how offset/limit interact), or filtering semantics. The minimal statement leaves the agent uninformed about important details.

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 0%, yet the description only says 'with pagination and filtering', which vaguely hints at limit/offset for pagination and fields/service/include_deleted for filtering. It fails to explain what each parameter does, e.g., meaning of 'fields' or 'service', leaving the agent with no understanding of how to use parameters correctly.

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?

Description clearly states 'List reports from OpenMetadata', specifying verb and resource. Distinguishes from siblings like list_tables or list_charts by focusing on reports. However, lacks explanation of what constitutes a report in OpenMetadata, which may cause slight ambiguity.

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?

Description mentions pagination and filtering features but provides no guidance on when to use this tool versus get_report, create_report, or other list_* tools. No alternatives or exclusions are given, relying solely on implied usage.

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