aras_advance_change

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

The description is transparent about the action (voting active activity) and the dryRun preview. It warns that pending activities have no effect, but does not mention potential side effects like state transitions after voting.

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, two sentences, and well-structured. It covers the essential behavior 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?

The description is fairly complete for a specialized tool. It explains the purpose, the condition, and the dryRun behavior. It does not describe the return value, but that is not required without an output schema.

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 already describes 'via', and the description explains dryRun. However, 'changeId' and 'commenti' are not clarified, leaving gaps. Overall, the description adds moderate value beyond the schema.

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 (advance) and the resource (ECR/ECN), specifying that it votes the active activity. This distinguishes it from the sibling tool aras_vote_activity, which is more general.

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?

It explains the condition (only one active activity, pending ones are downstream) and the dryRun feature, giving practical guidance. It does not explicitly compare with vote_activity, but the specificity implies when to use it.

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