Create Poem

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

Adds specific behavioral detail beyond the destructiveHint annotation: posting hides the previous poem from readers. Does not specify if author can still access it, but still provides useful context.

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?

Two sentences, no fluff. All information is relevant and front-loaded. Every sentence serves a purpose.

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 creation tool with one parameter and no output schema, the description fully covers purpose, parameter usage, and a key behavioral consequence. No gaps.

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?

Describes the content parameter's structure (first line is title, rest is body), adding meaning beyond the schema description. Schema coverage is 100%, so baseline 3, but the extra detail justifies 4.

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 it creates a poem, defines it as a casual short note, and distinguishes from sibling tools (get-poem, search-poems) by being the creation action.

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?

Implied usage: use to create a poem, not to retrieve. Mentions side effect of hiding previous poem, but lacks explicit when-to-use vs alternatives, though context makes it clear.

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