sdcloud_list_schedulers

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

No annotations provided; the description does not disclose behavioral traits such as whether it's a read-only operation, response size limits, pagination default behavior, or rate limits. For a listing operation, this is insufficient.

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 a single, concise sentence (10 words) that front-loads the primary action and resource. Every word earns its place; no excess information.

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 without output schema, the description is adequate but could mention that it returns a list of scheduler objects, that it's read-only, or default pagination behavior. Lacks completeness in covering expected outcomes.

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 description coverage is 100% (all 5 parameters have descriptions in the schema). The description adds no new meaning beyond 'optional pagination, filtering, and sorting', so baseline score 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 clearly states the verb 'List' and the resource 'scheduler objects', and mentions optional features like pagination, filtering, and sorting. It distinguishes from sibling tools (e.g., sdcloud_create_scheduler, sdcloud_get_scheduler).

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 usage for listing schedulers but provides no explicit guidance on when to use or not use this tool, nor alternatives. No context about prerequisites or suitability compared to siblings.

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