faf_auto

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

Lists the sub-tools run, but does not explain error handling, rollback, idempotency, or whether it is safe to run multiple times. Annotations already indicate non-destructive; description adds minimal behavioral context.

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?

Very concise, one sentence with clear purpose. Emojis and exclamation add flair but reduce formality slightly; still effective.

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?

Sufficient for a composite convenience tool, but lacks details on execution order, failure behavior, and prerequisites. No output schema needed, but more context would improve decision-making.

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 coverage is 100%, so description adds no additional meaning to parameters. Baseline of 3 is appropriate.

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 explicitly states it runs a sequence of specific sub-tools (init, sync, formats, bi-sync, score) in one command, clearly distinguishing it from sibling tools that perform individual steps.

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?

Implicitly indicates this is for a full workflow by saying 'in one go', but does not explicitly state when to use it versus individual tools or when not to use it.

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