list_heu_documents

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

No annotations provided, so description must convey behavioral traits. It does not explicitly state safety (e.g., read-only) or side effects, but the action 'list' implies no destructive behavior. Basic transparency is adequate for a listing 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?

Two sentences with no redundant words. Purpose is stated first, followed by important usage warning. Every sentence adds value.

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?

Given 5 optional parameters and no output schema, the description covers the key behavior (listing with filters) and the critical constraint on date parameters. It does not explain return format, which is acceptable as the tool likely returns document/template objects consistent with other tools.

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%, but description adds critical usage context for 'created_from' and 'created_to' (must be paired). Other parameters ('type', 'sort', 'have_editors_signed') are sufficiently described in both schema and description.

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 the tool lists HEU native documents/templates with optional filters. It distinguishes from sibling tools like 'create_heu_document' or 'get_heu_document' by specifying 'list' and 'nativi HEU'.

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?

Explicit guidance on using date range parameters: always pass both 'created_from' and 'created_to' together, and omit both to get all documents. This is clear usage advice, though it does not mention when to prefer this over other list tools.

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