telos_audit

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

No annotations present, so the description bears full responsibility. It discloses the 100-entry cap, the return structure including a 'capped' boolean, and the required ordering of parameters.

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?

Well-structured with summary, cap note, args, and returns sections. Concise enough but could be slightly tighter.

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?

With 2 parameters and an output schema (implicit from description), the description covers all necessary context: input format, cap, return shape. No gaps.

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 0%, but the description fully explains both parameters: ISO-8601 format with examples, and the constraint that end_iso must be later than start_iso.

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 it 'Return audit chain entries within a time window' using a specific verb and resource. The sibling tools (telos_score, telos_verify, etc.) have distinct names, so no confusion.

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?

Describes when to use (audit queries) and provides a when-not (deeper queries via the resource). Does not explicitly contrast with siblings but their names imply different functions.

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