things_create_from_template

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

Annotations already provide readOnlyHint=false and idempotentHint=true, and the description adds valuable behavior beyond them: 'URL receipt confirms dispatch only,' no read-back or returned IDs, and 'never retry with a new request ID.' This aligns with and enriches the idempotency annotation without contradicting it.

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?

Five short sentences are front-loaded with the primary purpose and every sentence earns its place. 'Requires writes' is mildly redundant with the annotation, but the overall density is excellent.

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?

Despite the deeply nested schema, the description covers the essential dispatch semantics, idempotency constraints, and the critical limitation that there is no read-back or returned ID. Since an output schema is present and annotations carry the safety profile, nothing needed for correct invocation is missing.

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?

With schema description coverage at 0%, the description compensates by explaining meaningful semantics: the item is a structured to-do or project, checklist rows and initial headings are supported, and requestId carries idempotent retry meaning ('never retry with a new request ID'). It leaves detailed nested fields to the schema, but those field names are self-explanatory.

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 opens with a specific action and resource: 'Send one structured to-do or project to Things,' and adds distinct capabilities like checklist rows and initial project headings. It does not explicitly differentiate from sibling creation tools such as things_create_item or clarify the 'from_template' name, so it falls short of a 5.

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 conveys clear context for use—structured to-dos/projects with checklists and headings—but gives no explicit when-to-use versus alternatives or when-not guidance. The retry warning is operational guidance rather than tool-selection guidance.

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