list_records

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

No annotations are provided, so the description carries full burden. It discloses that this is a query operation (implied read-only) and mentions filtering capabilities, which is useful. However, it doesn't describe pagination behavior (implied by pageNumber/pageSize parameters but not explained), rate limits, authentication requirements, or error conditions. For a tool with 9 parameters and no annotation coverage, this leaves significant behavioral gaps.

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 two sentences that efficiently state the core purpose and key capability (filtering). Every phrase adds value: 'Domain Name System (DNS) records of a website' specifies the resource, 'including the record value, priority, and authentication configurations' adds detail, and the filtering sentence highlights important parameters. It's appropriately sized and front-loaded with the main function.

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 the tool's complexity (9 parameters, no output schema, no annotations), the description is moderately complete. It covers the basic purpose and filtering capability but lacks information about return format, pagination behavior, error handling, and relationship to sibling tools. With no output schema, the description should ideally mention what the query returns, but it only hints at it ('including the record value, priority, and authentication configurations'). This leaves gaps for effective agent usage.

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%, so the schema already documents all 9 parameters thoroughly. The description adds marginal value by mentioning 'RecordName and RecordMatchType' as filtering examples, but doesn't provide additional context beyond what's in the schema. It doesn't explain parameter interactions or usage patterns. Baseline 3 is appropriate when the schema does the heavy lifting.

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 purpose: 'Queries a list of Domain Name System (DNS) records of a website' with specific details about what information is included (record value, priority, authentication configurations). It distinguishes itself from sibling tools like 'get_record' (singular) and 'er_record_list' (different scope), but doesn't explicitly contrast with all filtering alternatives. The verb 'queries' is specific and appropriate.

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 implies usage context through 'Supports filtering by specifying parameters such as RecordName and RecordMatchType,' suggesting this is for filtered listing operations. However, it doesn't explicitly state when to use this tool versus alternatives like 'list_sites' (for site enumeration) or 'get_record' (for single record retrieval), nor does it mention prerequisites like needing a siteId first. The guidance is present but incomplete.

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