Get Driver

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

Annotations already declare this as read-only and idempotent. The description adds that the full configuration including persona prompt is returned, which is useful context. No mention of error behavior, but given the simple read-only nature, this is acceptable and adds some value beyond 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 compact and front-loaded with the primary purpose. The additional sentence and Args section add value without redundancy or unnecessary detail.

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 simple getter with one parameter, an output schema, and read-only annotations, the description covers the core behavior and return content. It doesn't discuss error handling, but the output schema and simplicity mitigate the gap, making the tool adequately complete.

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 schema has a single required string parameter 'name' with no description. The description's Args section restates that name is the driver name, providing minimal additional meaning. It doesn't add details like uniqueness or format, but for a simple identifier it suffices given the low schema coverage.

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 clearly states the tool retrieves an existing driver persona by name, returning its full configuration including the persona prompt. This distinguishes it from sibling list_drivers, which lists drivers, and create_or_update_driver, which creates/updates.

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 implies usage for fetching a previously configured driver by name. It doesn't explicitly mention alternatives or when not to use it, but the context is clear enough: use when you need a specific driver's full config. It provides no exclusion rules but the intended use case is evident.

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