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

The readOnlyHint already establishes this is a safe read, so the bar is lower. The description adds genuine behavioral context beyond that: values omitted keep the defaults shown, and the consumed shape is { id, values }, which tells the agent what it will need from the result when creating a project.

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, front-loaded with the resource identity before the workflow instruction. The parenthetical example list is long and could be trimmed, but each example is illustrative rather than filler, so nothing is seriously wasteful.

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 zero-parameter read tool with annotations and no output schema, the description covers what the templates are and how to use them downstream. It does not spell out the exact return shape (e.g., whether each template carries an id and default values), which is the only material gap.

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?

The tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description's mention of the { id, values } shape is supplementary output-related context, not a substitute for parameter documentation.

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 names the resource concretely ('ready-made stories to fill in') and enumerates representative examples (trip with stops, visited countries, data maps), so an agent understands these are project templates. It differentiates from siblings by tying the output to studio_create_project, though it never states an explicit verb like 'list' or 'returns' for the tool itself.

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?

It gives explicit downstream usage: 'Pass one to studio_create_project as template { id, values }', which tells the agent the workflow this tool feeds. It lacks any when-not guidance or differentiation from nearby list tools (studio_list_examples, studio_list_capabilities), so the routing is clear but not exhaustive.

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