List Cloud Sync Tasks

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

Annotations already declare readOnlyHint=true, and the description adds a valuable behavioral guarantee: 'Credentials, tokens, and secrets are deliberately never included.' This goes beyond annotations by assuring users about sensitive data handling. It does not cover all behaviors (e.g., pagination) but provides useful 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?

The description is two sentences, front-loaded with the action and resource, and every clause adds value (field list, provider examples, credential exclusion). No wasted words.

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 simple list tool with one parameter, an output schema, and read-only annotations, the description sufficiently covers what the tool does and important caveats (no secrets). It doesn't need to explain return values because an output schema exists.

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% with the response_format parameter fully described in the schema, including enum values and default. The description itself adds no extra parameter semantics, so the baseline of 3 applies.

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 uses a specific verb ('List') and resource ('configured cloud sync tasks'), and elaborates with concrete field details (local path, direction, provider, schedule, last-run state) and provider examples (S3, Google Drive, Backblaze). This clearly distinguishes it from sibling list tools.

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 implies when to use it (whenever cloud sync task info is needed) but does not explicitly mention alternatives or exclusions. It lacks guidance on when not to use it or how it differs from other list tools beyond the resource type.

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