project_template_list

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

Discloses read-only nature, safe to retry, return structure with fields, sorting order, and edge case (empty array when no Templates folder). No annotations provided, so description carries full burden.

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?

Three sentences plus example, no wasted words. Purpose, exclusion, return format, and behavior are front-loaded and clear.

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 parameterless tool with no annotations or output schema, the description covers purpose, behavior, return format, sorting, edge case, and provides an example. Fully adequate.

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?

No parameters exist; description adds value by explicitly stating 'call with no args' and giving an example. Schema coverage is trivially 100%, baseline 3; description provides helpful context.

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 listing saved project templates, distinguishes from ordinary projects, and explains what counts (templates with parseable fence).

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 warns not to use for ordinary projects and names the alternative tool (project_list). Clear when to use.

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