telos.loop.ledger

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It clearly states the tool is read-only, requires no authentication, has no external side effects, and returns a JSON ledger. No contradictions.

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 succinct sentences with no superfluous words. The purpose, usage, and behavioral traits are front-loaded. Every sentence earns its place.

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?

The tool has no output schema, so the description should explain the return value in detail. 'JSON loop-ledger convention' is too vague for an agent to know the structure or fields. Additionally, the description does not clarify what 'bounded scheduled runs' means or how the state is managed. More context is needed for a complete understanding.

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 has zero parameters, so the input schema is fully covered. The description adds value by explaining the return type ('JSON loop-ledger convention'), which is helpful given the lack of an output schema. Baseline for 0 params is 4.

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 is for durable state across agent loops and scheduled runs, with a specific verb ('loop ledger'). However, 'loop-ledger convention' is vague and could be more explicit, and sibling tools like 'telos.context.envelope' or 'telos.catalog' might also relate to state, but no differentiation is provided.

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 explicitly states when to use ('when an agent loop needs durable state'), implying read-only usage. It does not mention when not to use or list alternatives among the many sibling tools, but the context is clear enough for an agent.

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