list_configs

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description adds no new behavioral context beyond that. It does not disclose that the result is paginated, what fields are returned, or that 'all' actually means a page of results given the page and per_page parameters.

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 clear sentence with no fluff and leads with the action. It is appropriately short for a simple list tool, though it could have added a brief note about pagination or return shape without becoming verbose.

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 is simple, all parameters are optional, and annotations cover the safety profile. However, there is no output schema and no mention of pagination, sorting defaults, or what a 'configuration' result looks like, leaving minor but real gaps for an agent deciding how to inspect results.

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 0%, so the description is the only prose source of parameter meaning, but it says nothing about page, sort_by, per_page, or sort_order. The schema provides types and enums but no semantic explanation, and the description does not compensate.

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 states a specific action ('List') and a clear resource ('saved scrape configurations'). It distinguishes from single-config tools like get_config by using 'all', though it does not explicitly mention any sibling tool or filtering difference.

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?

There is no guidance on when to use this tool versus alternatives such as get_config, create_config, or list_schemas. The description implies a browse/enumerate use case but never states conditions, exclusions, or preferred alternatives.

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