Delimit Resource Drivers

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds value by stating the underlying call (ai.data_plane.list_drivers) and clarifying the return shape, which goes beyond the annotations.

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 well structured with clear sections, front-loaded purpose, and no filler. Every section earns its place: when to use, when not to use, sibling contrast, side effects, args, and returns.

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?

For a zero-parameter read-only inventory tool, the description is complete: it explains what the tool returns, how it differs from siblings, and what side effects to expect. The presence of an output schema also reduces the need to document return values further.

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?

The tool has zero parameters, so there is no parameter semantics burden. The description explicitly states 'Args: None', which is consistent with the empty input schema and gives the agent certainty.

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 verb and resource: 'List available data plane drivers and their resource schemas.' It also explicitly contrasts with sibling tools delimit_resource_list and delimit_resource_get, making it unambiguous which tool is which.

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 gives explicit 'When to use', 'When NOT to use', and names the exact alternative tools for reading data. This is ideal routing guidance for an agent deciding among many delimit_* siblings.

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