get_episode

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

No annotations; description carries full burden. It discloses return content (events, diff, file state) but does not mention beahvior on missing ID, idempotency, or side effects. Sufficient for a simple retrieval but lacks details on error handling or performance.

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?

Single sentence of 22 words, efficiently front-loaded with core purpose. No redundant or extraneous information.

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 simple structure (1 parameter, no output schema, no annotations), description covers return content well. Missing details on error cases or limitations, but overall sufficient for intended use.

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 0% - parameter undocumented. Description only reuses parameter name 'episode_id' without adding format, source, or constraints. Fails to compensate for missing schema 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?

Description clearly states verb ('get'), resource ('episode'), and specifies scope ('Full detail ... includes all referenced events, diff, reconstructed file state'). It distinguishes from siblings like find_episodes which likely list episodes without full detail.

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?

Implied usage (retrieve episode by ID) but no explicit when to use vs alternatives like find_episodes or get_latest_events. Does not provide exclusions or context for decision-making.

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