templates_list

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds the MANAGE_GUILD permission requirement and warns that template names and descriptions are raw Discord data that should be reviewed before treating as instructions, which is valuable security context. It also specifies the return structure. No contradiction with annotations.

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 extremely concise with three labeled sections (Purpose, Requires, Returns), each sentence earning its place. It's front-loaded with the purpose and uses clear formatting.

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?

The description covers the core purpose, permission requirement, return shape, and includes a security warning about untrusted text. However, it doesn't explain how this tool differs from sibling template tools (e.g., when to use templates_get instead), which is a minor gap for an agent choosing among many template tools.

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 fully describes the only parameter (guild_id) with a description, so the description adds limited value. It clarifies that templates belong to the caller bot and applies to one guild, but this is largely redundant with the schema and purpose. Baseline 3 due to high schema coverage.

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 lists the caller bot's Guild Templates for one guild, with a specific verb, resource, and scope. It does not explicitly distinguish from sibling template tools like templates_get or templates_inspect, 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 provides the permission requirement (MANAGE_GUILD) and mentions the return shape, but it gives no explicit guidance on when to use this tool versus alternatives such as templates_get or templates_create. The usage is implied by the purpose, so it's a 3.

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