list_available_reports

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

No annotations are provided, so the description carries the full burden. It usefully discloses that results are filtered by the caller's role permissions ('this role may download'), which is real behavioral context. It does not state that the operation is read-only, whether the list is paginated, or what is returned.

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?

Two short sentences, front-loaded with the primary purpose and followed immediately by the one detail an agent cannot get from the schema. No wasted 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?

For a single-parameter, read-only listing tool with no output schema, the description covers purpose and the critical enum values. The remaining gap is minor: no statement of read-only nature or return shape, but nothing essential is missing for correct invocation.

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 0% and the schema declares 'domain' as a bare string with no enum, so the description is the only source of parameter meaning. It supplies the allowed values ('management' or 'billing'), which is essential to calling the tool correctly, though it does not explain what each domain covers.

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 (list) and resource (report types) with a clear scope qualifier ('this role may download'). It implicitly distinguishes the tool from download_report and get_report_job_status by being the discovery step, but it never names them explicitly.

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?

Usage is implied: an agent would call this to discover what is downloadable before invoking download_report. However, there is no explicit when-to-use statement, no mention of prerequisites, and no reference to the sibling tools as alternatives.

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