List Poe models

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description correctly conveys a non-mutating enumeration. It adds the filtering semantics but says nothing about result size, pagination, or completeness of the returned model list, which matters for an enumeration tool.

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?

A single sentence that front-loads the core action and appends the optional filter behavior with concrete examples. No wasted words or redundancy.

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 read-only list tool with one optional, fully documented parameter and no output schema, the definition covers what an agent needs to invoke it correctly. Only minor gaps (no mention of result volume or pagination) remain.

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 the 'search' parameter is already documented as a case-insensitive filter on name/description. The description supplements this with concrete example values ('veo', 'image', 'eleven'), which is genuinely useful, but adds no further syntax or constraint detail.

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?

Specific verb ('List') plus resource ('bot/model names available through the Poe API'), and the optional filtering behavior is stated up front. The resource is clearly distinct from the generation-oriented siblings (generate_image, generate_video, etc.), though the description never explicitly contrasts itself with them.

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 phrase 'optionally filtered by a search term' implies how to narrow results, but there is no explicit statement of when to call this tool versus the sibling generation tools or when the search filter is warranted. Usage is inferable rather than spelled out.

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