delimit_resource_list

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

No annotations exist, so description should disclose behavioral traits. It only states the basic listing operation without mentioning read-only nature, authentication requirements, rate limits, or pagination. Insufficient for a mutation-free query tool.

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?

Extremely concise: two short sentences plus a line of examples. Front-loaded with purpose, followed by specific driver and resource types. No wasted words.

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 6 parameters and an output schema, description gives high-level purpose and key details. Could be improved by mentioning output format or filtering behavior, but is largely complete for a listing 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 has 100% description coverage, so baseline is 3. Description repeats some parameter info (drivers, resources) but adds no new meaning or constraints beyond what schema provides.

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?

Description clearly states verb ('List'), resource ('resources from a connected system'), and specifies drivers (github) and resource types (repos, pull_requests, issues, workflows). Distinguishes from sibling tools like 'delimit_resource_get' and 'delimit_resource_drivers' by implying a listing operation.

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 context on when to use (connected system with specific drivers and resources) but does not explicitly state alternatives or when not to use. No mention of sibling tools for comparison, limiting guidance for tool selection.

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