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

With no annotations, the description partially covers behavior by noting the approval process for first use and ongoing use. It does not disclose whether adding a rule overrides existing rules, reverts, or has other side effects. Some behavioral context is provided but not exhaustive.

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 concise with two sentences plus a brief note. It is front-loaded with the core action, includes examples, and provides essential behavioral context without unnecessary fluff.

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 4 required parameters, no output schema, and no annotations, the description covers purpose, usage, and approval behavior. It lacks details on return values or whether the rule replaces existing ones, but it is fairly complete for a straightforward add-rule tool.

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 description coverage is 100%, so baseline is 3. The description adds value by giving concrete examples for style_rule and output_format parameters (e.g., 'Use bullet points', 'changelog'), which helps the agent select appropriate values beyond the schema's generic descriptions.

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 'Manually add a style rule to a pipeline,' which is a specific verb+resource. Examples like 'always use bullet points' help clarify the tool's purpose, but it does not explicitly differentiate from sibling tools such as update_pipeline, though the intent is distinct.

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 provides explicit guidance on when to use the tool ('Use when user says...') with concrete examples. It also includes note about write-tier approval requirements. However, it lacks explicit instructions on when not to use it or alternatives.

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