template_list

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

As no annotations are provided, the description must convey behavioral traits. It indicates a read operation ('List all available templates'), which is safe. However, it does not mention if the list is paginated or if there are any rate limits, though the simplicity of the tool reduces the need.

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?

The description is concise and well-structured with bullet points and icons. However, the use of emojis may not be parsed optimally by all agents. The main action is front-loaded and every sentence adds value.

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 simple list tool with no output schema, the description covers the key aspects: what it lists and how to use it (optional search). It mentions 'template IDs and sources' in the best-for section, which gives a hint about the return data. Could be more explicit about the return format, but 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?

The input schema covers 100% of parameters with a clear description for 'searchQuery'. The tool description adds no extra meaning beyond 'filter templates by name and description', so it meets the baseline but does not exceed.

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 'List all available templates' and provides specific use cases like 'Discovering available templates' and 'Finding template IDs and sources', which precisely identifies the tool's function and distinguishes it from siblings.

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?

Comprehensive guidelines with 'Best for', 'Not for', alternatives, next steps, and related tools. This gives clear context on when to use this tool versus others, such as 'service_create_from_repo'.

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