Poet (pydantic-ai + sampling)

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

No annotations are provided, so the description carries the behavioral burden. It does disclose that the LLM comes from the client via MCP sampling, which is useful, but it does not mention nondeterminism, latency, or potential client-side approval requirements.

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 one concise sentence with the core action front-loaded. It adds useful implementation context about MCP sampling and contains no unnecessary filler.

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 one-parameter tool, the description provides enough context to understand what the tool does and where the model comes from. It could more explicitly connect the theme parameter to the generated poem, but the overall behavior is adequately specified.

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?

The schema has one required 'theme' parameter with no description and 0% schema description coverage. The tool description never mentions 'theme' or explains that the poem should be about that theme, so it fails to compensate for the missing parameter 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?

The description clearly states that a pydantic-ai agent writes a short rhyming poem, which is a specific verb plus resource. This distinguishes it from the sibling tools, none of which are poem generation tools.

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 need for a rhyming poem is implied by the description, but there is no explicit guidance about when to use this tool versus alternatives, nor any stated exclusions or prerequisites.

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