List clauses

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

No annotations are provided, so the description must carry behavioral disclosure. It does state ordering ('newest categories first') and the read-only nature implied by 'List', but the ordering phrase is ambiguous and pagination, return format, or potential limits are not disclosed. It adds some behavior context but not full clarity.

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 and the core action is front-loaded. The phrase 'newest categories first' is somewhat awkward but the description remains appropriately compact.

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 list tool, the description covers the core scope and filtering behavior. However, the ambiguous ordering phrase and complete lack of output/return details, especially with no output schema or annotations, leave a meaningful gap for an agent trying to reliably use the result.

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 schema has one undocumented 'category' string with 0% description coverage. The description compensates by explaining that the list can be 'narrowed to one category,' giving the parameter a clear role. It does not enumerate valid values or format, but for a simple optional filter this is sufficient.

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?

Description uses a specific verb and object: 'List every clause.' It also states the optional category filter, which clearly distinguishes this broad listing tool from focused retrieval tools like clause_get or clause_search. The resource and scope are immediately understandable.

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: use this to list all clauses, optionally filtered by category. However, it does not explicitly contrast with clause_search or clause_get, and provides no when-not-to-use guidance. Context is present but exclusions and alternatives are left to inference.

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