Render a quote as a shareable image

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

With no annotations provided, the description carries full behavioral disclosure. It clearly states the output is a PNG file, it is written to a temp file, copied to the macOS clipboard, and returns only the file path as text (never the image itself). This gives the agent a complete picture of side effects and return behavior.

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 three sentences long and packs in the core purpose, the parameter relationship, and the return behavior. It is front-loaded and every sentence contributes, though slightly more verbose than strictly necessary.

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?

Given 4 optional parameters, no output schema, and no annotations, the description is highly complete. It explains what the tool returns (file path text), the macOS clipboard side effect, and how the mode selection works, so an agent can invoke it confidently without additional documentation.

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 baseline is 3. The description adds minimal new meaning beyond the schema; it reiterates the situation/verse relationship already in the schema. It does add some context about caption formatting (italic, one line, shrunk/clipped) but this is marginal.

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 explicitly states the tool renders one verse as a PNG quote card, writes it to a temp file, and puts it on the clipboard. This is a specific verb+resource (render verse) that clearly distinguishes it from siblings like find_quote, random_quote, and list_themes.

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 explains two usage modes (situation or verse) and the intended use case (pasting into Slack or a doc). It does not explicitly name alternatives or when not to use, but the context is clear enough for an agent to select this over siblings.

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