add_driver

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

With no annotations, the description must disclose behavioral traits. It only states that it adds a driver, implying mutation, but does not explain side effects (e.g., overwriting existing drivers, dependencies, or required context). The minimal description is insufficient 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?

The description is extremely brief and front-loaded with the core action, which is good for conciseness. However, it is too short to convey necessary usage and parameter context, making it under-specified rather than efficiently concise.

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 tool with four parameters, no annotations, and a potentially complex effect (drivers in Blender), the description is grossly incomplete. It fails to cover parameter semantics, usage context, or behavioral nuances, leaving the agent without adequate information to call the tool correctly.

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 no parameter descriptions (coverage 0%), so the description must compensate. It only gives an example for data_path, leaving object_name, index, and expression unexplained. This is a notable gap for a multi-parameter tool.

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 action: 'Add a driver to an object property.' It identifies a specific verb and resource, and the example 'data_path e.g. 'location'' helps convey intent. However, it does not distinguish this from similar tools like set_custom_property or remove_driver beyond the verb.

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 like remove_driver or set_custom_property. There is no mention of prerequisites, scenarios, or exclusions, leaving the agent to infer usage from the name alone.

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