list_templates

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only mentions the return type (Dictionary with list of templates and metadata) without addressing permissions, pagination, or whether the list is scoped to the user's account. This is minimal and insufficient for a complete understanding.

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 and front-loaded with a clear one-sentence purpose, followed by an Args/Returns structure. Every word earns its place, with no wasted text.

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 one-parameter tool with an output schema, the description covers the essential purpose, parameter, and return format. It lacks guidance on when to use the tool, but given the low complexity, it is reasonably complete. Additional notes on access scope would make it stronger.

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 description explains that search_text 'filters templates by name,' adding meaningful semantics beyond the schema's bare type definition. Since schema coverage is 0%, this description is essential and compensates well, though it could add details like case sensitivity or partial matching.

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 'List available DocuSign templates' with a specific verb and resource. This distinguishes it from sibling tools like create_template or get_template_definition, which perform different operations on templates.

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 implies usage for enumerating templates but does not explicitly mention when to use this tool over alternatives. There is no reference to sibling tools or exclusions, leaving usage guidance implicit rather than explicit.

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