list_reports

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic operation (listing metadata) but does not mention whether this is a read-only operation, if authentication via spxKey is required, what happens with missing keys, rate limits, pagination, or any side effects. The implied behavior is minimal.

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?

The description is a single 11-word sentence that is front-loaded with the verb 'List' and the main resource. Every word is necessary and there is no redundancy or wasted text.

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?

The tool has 3 optional parameters and no output schema. The description fails to mention whether the list is paginated, filtered, or ordered; what the metadata structure looks like; or any prerequisites such as needing an active SPX key. Agents are left to guess the return format and behavior.

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 schema provides descriptions for spxKey and baseUrl (67% coverage). The description adds context that the endpoint is 'embedded web UI data', which helps clarify the purpose of baseUrl and spxKey. However, it does not elaborate on timeoutMs or provide parameter-specific guidance beyond what the schema already offers. Baseline 3 is appropriate given the coverage.

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 uses a specific verb 'List' and identifies the resource 'SPX report metadata' and the source 'embedded web UI data endpoint'. This clearly distinguishes it from siblings like 'get_report_metadata' (which implies retrieving a single report's metadata) and 'analyze_report' (which implies deeper analysis).

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 provides no guidance on when to use this tool versus alternatives such as get_report_metadata for a single report or analyze_report for analysis. It does not state prerequisites, limitations, or scenarios where this tool is appropriate or inappropriate.

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