delimit_resource_drivers

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

No annotations are available, so the description must carry the burden. It states 'List', implying a read-only operation with no side effects. While this is clear for a simple listing tool, it lacks details such as authentication requirements or behavior when no drivers are available.

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 concise sentence that front-loads the purpose ('List available data plane drivers'). Every word is necessary and no additional fluff is present.

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 has no parameters and the output schema exists, the description sufficiently explains what is returned (drivers and their schemas). It is complete enough for a tool of this simplicity, though additional context about the data plane drivers could enhance understanding.

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 input schema has zero parameters, and the description does not need to explain parameter details. Schema coverage is 100% (since there are none), and the baseline for no parameters is 4, which is appropriate here.

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 'List available data plane drivers and their resource schemas' clearly states the action (list) and the specific resources (data plane drivers and their schemas). It distinguishes itself from sibling tools like delimit_resource_list (which likely lists resources) by focusing on drivers and their schemas.

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?

No guidance is provided on when to use this tool versus alternatives. Among many sibling tools including delimit_resource_list and others, explicit context about the typical use case or when not to use would help an agent decide appropriately.

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