List Organization Doc Templates

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

Annotations mark this read-only, and the description adds that each template's full content is returned, which is useful beyond the annotation. It does not cover pagination or result size, but those are not critical for a simple list tool.

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?

A single 17-word sentence states the action, the optional filter, and the return payload. No filler or redundancy.

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 one optional parameter and no output schema, the description is sufficient: it names the resource, the filter, and what is returned. Minor omissions like pagination or a pointer to get_org_doc_template for single-template retrieval are not critical.

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?

Schema coverage is 100% and the pageType description already lists all valid values, so the schema carries the parameter semantics. The description only restates the optional filter without adding new detail.

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 verb 'List' and resource 'organization's documentation page templates' clearly identify a read-only enumeration. The optional pageType filter adds precision, but it does not explicitly differentiate from sibling get_org_doc_template or list_documentations.

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 use for listing all or filtered templates, but it never states when to choose this over get_org_doc_template or list_documentations. The only usage guidance is the optional pageType filter, which is parameter-level rather than tool-selection guidance.

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