telos_replay

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

Discloses async behavior ('Returns immediately with a job id; poll the result'), includes return keys. No annotations provided, so description carries the burden well. Could mention side effects or permissions.

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 and docstring sections (Args, Returns). Slightly verbose but front-loads purpose. 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?

Covers input parameters, async behavior, and return format. Lacks clarification on CCRS and Mode C terminology. Output schema presumed from description.

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 description adds detailed semantics: 'receipt_id: ID of the receipt to replay against' and 'alt_config_path: Path to the alternate config (YAML) to apply.' Adds meaning beyond property names.

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?

Explicitly states 'Queue a CCRS counterfactual replay against an alternate config,' with specific verb and resource. Distinct from siblings like telos_score and telos_verify, which are about scoring and verifying.

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?

Implies usage via description of functionality but no explicit when-to-use or alternatives. No exclusions given.

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