delimit_resource_list

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

No annotations provided, but description states 'read-only network calls' and internal driver methods. Discloses side effects and internal behavior sufficiently for safe invocation.

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?

Concise at ~100 words, uses clear sections, front-loaded main purpose. No unnecessary sentences.

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 full schema descriptions and output schema existence, the description covers all necessary context: purpose, usage, side effects, and sibling differentiation.

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 coverage is 100% with detailed param descriptions. Description adds usage context (e.g., 'repo required for workflow listing') but does not substantially extend parameter meaning beyond schema.

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 'List resources from a connected data-plane system' with specific examples (repos, PRs, issues, workflow runs). Distinguishes from siblings by naming delimit_resource_get and delimit_resource_drivers.

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?

Explicit 'When to use' and 'When NOT to use' sections with alternative tools named. Sibling contrast further clarifies when to use this tool versus similar ones.

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