ptero_ai_list_servers

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

No annotations provided. Description mentions 'safe defaults' suggesting non-destructive behavior but does not disclose pagination behavior, rate limits, authentication requirements, or response size constraints beyond a vague 'avoid huge responses'.

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?

Extremely concise single sentence. Front-loaded with purpose. However, it sacrifices necessary detail; additional sentences would improve utility without losing conciseness.

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?

Tool has output schema (not shown), but description provides minimal context. For a list endpoint with only two parameters, more guidance on response format, maximum per_page, or relationship to sibling tools is needed for competent use.

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 0%; description fails to explain the two parameters (page, per_page) and their defaults. 'Safe defaults' is vague and does not compensate for missing schema documentation.

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?

Clearly states 'list servers' with qualifiers 'compact' and 'safe defaults'. Distinguishes from search tools (ptero_ai_search_servers) implicitly but does not explicitly contrast with sibling list tools (ptero_app_get_servers).

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 explicit guidance on when to use vs alternatives. The phrase 'safe defaults' hints at conservative pagination but does not explain when to prefer this over search or other list endpoints.

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