sync_ftp_users

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

With no annotations and no behavioral detail, the description carries the full burden and provides nothing. It does not disclose what synchronization entails, whether it overwrites existing FTP users, what permissions are required, or what side effects occur.

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 short but under-specified rather than concise. It does not front-load any useful information beyond the tool name, so the two words do not earn their place in helping an agent understand the operation.

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?

There is no annotation or output schema to compensate for the missing description. The definition is completely inadequate for explaining a state-changing synchronization operation, leaving the agent unable to know what the tool actually does or when it is safe to call.

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 tool has zero parameters and therefore no parameter semantics for the description to explain. Baseline for a 0-parameter tool is 4.

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 'Sync FTP users' essentially restates the tool name sync_ftp_users rather than defining what 'sync' means in this context. It does not distinguish the operation from sibling tools like list_ftp_users, update_ftp_user, or create_ftp_user.

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 about when to use this tool versus alternatives. The description does not mention prerequisites, source/destination, or any condition that would select it over list_ftp_users or update_ftp_user.

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