Letterheads and templates

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'Lists' strongly implies a safe read-only operation, and it adds useful context that the output indicates default templates for the signed-in user and internal documents. It still omits auth requirements, pagination behavior, or explicit confirmation of no side effects, leaving some gaps.

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 a single, front-loaded sentence that states the action and key output detail without any filler. Every phrase earns its place, and the structure makes the core purpose immediately 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 simple zero-parameter list tool with no output schema, the description tells the agent what is returned (document templates including letterheads, plus default usage information). It is nearly complete, though it could explicitly note that no input is required or mention authentication, which are minor gaps for such a straightforward operation.

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 tool takes zero parameters, and schema description coverage is 100% for the empty input schema. Per the rubric, a 0-parameter tool with no parameter semantics to explain receives a baseline of 4. The description adds no parameter details because none are needed.

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 states a specific verb ('Lists') and resource ('document templates in Clio including letterheads'), making the tool's purpose clear. It also notes the useful output detail about which template is used for the signed-in user and internal documents. However, it does not explicitly distinguish this list tool from sibling tools like clio_document_create_from_letterhead, so a 4 rather than 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 only explains what the tool does, not when or why an agent should choose it over alternatives. There is no mention of prerequisites, exclusions, or related sibling tools such as clio_document_create_from_letterhead. This falls short of even implied usage guidance.

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