Get one template's content.json schema

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

Annotations already indicate readOnlyHint=true and openWorldHint=false. The description adds that it returns a scene outline and hard rules, which are behavioral details beyond the annotations. It does not mention any destructive actions, which aligns with readOnlyHint. No contradictions.

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 with no extraneous information. The first sentence states the outcome concisely, and the second provides usage context. Very efficient.

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 the simple input (one parameter), good annotations, and no output schema, the description fully covers when to use, what it returns, and a critical warning. It is complete for the tool's purpose.

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 coverage is 100% with the parameter 'template' described as 'template id from list_templates'. The description does not add further semantics beyond what the schema provides, so baseline 3 is appropriate.

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 it returns the content.json schema, scene outline, and hard rules for ONE template. It uses specific verbs ('Return', 'Get') and resources ('content.json schema', 'scene outline', 'hard rules'), and the title reinforces this. The instruction to call it after the user picks a template and before writing content distinguishes it from sibling tools like list_templates or write_content.

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 states when to use: 'Call this after the user picked a template, before writing any content.' Also provides a clear exclusion: 'Each template has its OWN scene types — do not reuse another template's shape.' This guides the agent on proper sequencing and prevents misuse.

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