sdcloud_list_url_patterns

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

With no annotations, the description only conveys that it lists objects with optional modifiers. It does not disclose limits, default behavior, or implications of parameters like count=true.

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?

Single sentence, highly concise and front-loaded. Efficient for an agent to parse quickly.

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 list tool with 5 optional parameters and no output schema, the description is too sparse. It lacks return format, error handling, and relationship to sibling tools (e.g., get_url_pattern).

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%, so baseline is 3. The description adds minimal value beyond the schema by summarizing 'pagination, filtering, sorting' but does not explain syntax or provide examples.

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 'URL pattern objects', with optional pagination, filtering, and sorting. It distinguishes from sibling list tools (e.g., list_url_category_lists) by specifying the exact object type.

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 on when to use this vs alternatives like get_url_pattern or other list tools. Does not explain any prerequisites or context for using pagination/filtering/sorting.

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