list_contract_templates

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states 'List all contract templates' without mentioning pagination, default limit, return format, or whether archived templates are included. The word 'all' somewhat conflicts with the limit/offset parameters, though not explicitly.

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 sentence with no filler, front-loaded with the action and resource. It is appropriately concise and easy to parse, though extremely brief.

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 tool with no annotations and no output schema, the description is incomplete. It fails to explain when to use this tool over similar list operations, what the response contains, or how pagination behaves beyond the parameter descriptions. The agent would need to infer too much.

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 provides full descriptions for both limit and offset (100% schema coverage), so the baseline is 3. The description adds no additional meaning beyond the schema, but neither does it need to given the schema's completeness.

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 'List all contract templates' clearly specifies the verb (list) and resource (contract templates), making its purpose unambiguous. It distinguishes itself from related tools like get_contract_template and list_contracts by naming the exact resource, though it doesn't explicitly mention alternatives.

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 offers no guidance on when to use this tool versus alternatives such as list_contracts or list_contract_documents. There are no exclusions, prerequisites, or contextual hints provided, leaving the agent without direction for selection.

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