splunk_list_reports

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about pagination, sort order, permission requirements, or whether the listing includes disabled/unscheduled reports; only the implicit read-only nature of 'List' hints at behavior.

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?

Front-loaded with the core action in the first sentence, followed by a compact Args block. There is minor redundancy in restating parameter names, but each line adds value and there is no filler.

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?

An output schema exists, so return-value explanation is not required, and the two parameters are covered. Still, for a listing tool with no annotations and no differentiation from several sibling listers, the definition leaves gaps around result scope, pagination, and how 'reports' relates to 'saved searches' and 'alerts'.

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%, so the description must compensate, and it does partially: 'app: Optional app filter' and 'count: Maximum number of reports to retrieve' add real meaning over bare titles and defaults. However, it does not clarify whether 'app' expects an app name or ID, whether it accepts wildcards, or what the default count behavior is beyond the schema's default of 100.

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?

States a specific verb and resource: 'List scheduled and ad-hoc reports in the environment.' It is clear what the tool returns, but it never distinguishes 'reports' from sibling tools like splunk_list_saved_searches, splunk_list_alerts, and splunk_run_report, which an agent must disambiguate among.

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 gives no when-to-use guidance, no prerequisites, and does not name any alternative tool. The 'Args' block documents parameters but provides no context about when this listing should be preferred over splunk_list_saved_searches or splunk_get_scheduler_health.

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