list_metadata_simulations

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

Annotations only declare readOnlyHint=true, so the description rightly carries the behavioral load: it discloses sort order (newest first), result provenance (runs from here or the dashboard simulator), the exact per-row fields available, the re-run count, and explicitly which fields are NOT returned. That omission list is unusually useful. It stops short of describing pagination behavior or result-size limits.

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 purpose, then scope, then the field inventory, then the routing instruction — a sound structure with no filler sentences. The middle sentence is long because it enumerates return fields, but each clause conveys information an agent needs to interpret rows.

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?

There is no output schema, so the description must describe the return shape itself, and it does so field by field, including what is absent and how to retrieve it. Combined with named parameters living in the schema, an agent has everything needed to call and interpret this tool.

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 100% for all three parameters (page, search, per_page), so the schema already documents them. The description adds nothing about them — it only references the sibling tool's 'id' field, not its own params. Baseline 3 applies when the schema does all the work.

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 the listing drafts already scored on this account, newest first') and immediately bounds scope, including that rows come from both this tool and the dashboard Metadata Simulator. It is unmistakably distinct from the sibling get_metadata_simulation, which it names.

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?

Gives an explicit use condition ('Use this to find a past score without re-running it') and names the alternative plus the condition that selects it ('pass a row's "id" to get_metadata_simulation to read a draft in full'). Routing between the two tools is fully specified.

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