Publish a new Temp

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

Discloses key behaviors: publishes to temp.md, returns a stable public URL, automatically saves to .tempmd. Lacks details on permanence of URL or overwrite behavior, but for a new artifact tool, these are secondary.

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 that front-load the core functionality and supported types, then deliver usage guidelines. No filler 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?

Covers purpose, supported types, when-to-use, alternative, and record persistence. With no output schema, could briefly mention what the return value (URL) looks like, but 'stable public URL' is sufficient.

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 provides 100% coverage with good parameter descriptions. The description adds value by linking parameters to the .tempmd record and the new-artifact context, but does not repeat schema info.

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 the verb 'publish', resource 'artifact to temp.md', and supported formats (HTML, Markdown, CSV, Mermaid). Distinguishes from sibling 'update_temp' explicitly, making its scope unambiguous.

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?

Explicitly says 'Use only for a NEW artifact' and provides a condition (check .tempmd) and alternative tool (update_temp) for existing temps. Guides the agent on correct invocation context.

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