sync-application

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

The only behavioral trait disclosed is 'Blocked while ARGOCD_READ_ONLY=true', which is useful but insufficient. With no annotations provided, the description should explain that sync may change application state, potentially delete or update resources, and could be a long-running operation. It also fails to mention confirmation steps or the impact of parameters like 'force' and 'prune'.

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 very concise at two sentences, with no wasted words. It is structured as a single line of purpose followed by a condition. While short, it is efficient. However, the brevity sacrifices important context, preventing a perfect score.

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 mutation tool with 6 parameters, no output schema, and no annotations, the description is far too sparse. It does not explain return values, error conditions, the concept of 'target state', or how to verify success. Many sibling tools are read-only, so this tool's mutation behavior needs more explicit context.

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 input schema has 100% description coverage, meaning each parameter already has a description (e.g., 'Force sync (replace)', 'Prune resources during sync'). The tool description does not add any additional meaning or context, so the score is at baseline for well-documented schemas.

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 'Sync application to target state' with a specific verb ('Sync') and resource ('application'), making the tool's purpose immediately understandable. However, it does not differentiate from sibling tools like 'refresh-application' or 'terminate-application-operation', which could also modify application state.

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 such as 'refresh-application' or 'get-application-diff'. There is no mention of prerequisites, exclusions, or scenarios where this tool is inappropriate (e.g., read-only mode is hinted but not as a recommendation).

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