list_static_tables

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

With no annotations provided, the description carries the transparency burden. The statement about static tables containing pre-formatted HTML data gives a hint about output format, but it does not disclose pagination behavior, whether the list returns metadata or actual table content, or any default behaviors (e.g., default domain '0000'). It adds some context but remains incomplete.

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 exceptionally concise: two sentences that immediately convey the core purpose. No wasted words, and the verb-first structure is clear and scannable.

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 lacks an output schema and annotations, so the description is the only source of context. It fails to explain what fields are returned in the list, whether pagination applies, or how the filter parameters affect results. Given the 5 optional parameters and no output schema, the description is insufficiently complete for an agent to fully anticipate tool 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 input schema already provides descriptions for all five parameters, achieving 100% coverage. The description does not add any extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the tool's function with a specific verb and resource: 'List BPS static tables.' It also distinguishes the resource from other table types (e.g., SIMDASI tables) and adds context that static tables are pre-formatted HTML, which differentiates from alternative list tools.

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 verb 'List' implies usage for browsing static tables, and the mention of filters in the schema indicates potential uses. However, there is no explicit guidance on when to use this tool versus alternatives like 'get_static_table' or other 'list_*' tools, nor any when-not-to-use conditions.

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