list_curated

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

No annotations provided, yet the description fully covers behavior: returns a sorted list of exactly 5 IDs, non-destructive, no hidden side effects. Discloses that other F-tables are queryable via raw IDs.

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?

Well-organized with clear sections: purpose, when to use, example, returns. Every sentence adds value. No fluff, yet comprehensive.

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?

Given zero parameters and an output schema, the description is fully complete. It explains the tool's role in the ecosystem, the exact output, and even lists the tables. No gaps.

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?

Tool has no parameters; baseline is 4. Description adds value by explaining that no input is needed and clarifying that the output is a sorted list of specific F-table IDs. Schema coverage is 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?

Clearly states the tool lists 5 RBA F-table IDs with plain-English support. Distinguishes from siblings like search_tables (list all tables) and get_data/latest (query data). Verb+resource is specific and unambiguous.

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?

Provides 'When to use' section with three distinct scenarios (knowing supported tables, building UI/agent, planning calls). Implicitly suggests alternatives (e.g., search_tables for all tables, get_data for data) but lacks explicit 'when not to use' or alternative names.

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