ptero_ai_search_servers

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'fuzzy' and 'compact top matches', but does not explicitly state it is read-only, how scoring works, or what happens with no matches. The parameter min_score hints at filtering but is not explained in description.

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 sentence with zero waste: it front-loads the action and resource, specifies the search fields, and indicates output characteristic ('compact top matches'). Every phrase earns its place.

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?

While an output schema exists (handling return values), the description lacks guidance on parameter usage (e.g., what min_score does, pagination behavior). For a tool with 5 parameters and no schema descriptions, the description is insufficient for an agent to invoke it correctly.

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 0% meaning the schema provides no parameter descriptions. The tool description only lists the searchable fields (name/identifier/uuid/external_id) but does not explain any of the 5 parameters (query, limit, max_pages, per_page, min_score). This fails to add meaning beyond the schema.

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 'Fuzzy search servers by name/identifier/uuid/external_id' which specifies the verb (search), resource (servers), and search scope. This distinguishes it from sibling tools like ptero_ai_list_servers (simple listing) and ptero_ai_get_server_summary (specific server).

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 finding servers by fuzzy matching, but does not explicitly state when to use it versus alternatives like ptero_ai_list_servers or ptero_ai_search_users. No exclusions or conditional guidance provided.

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