klaket_find_moment

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

No annotations are provided, so the description fully describes the tool's behavior: it searches within a processed video and returns moments. It does not mention side effects, but as a search operation this is acceptable. There is no contradiction with annotations.

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 concise sentences with no wasted words. The first sentence describes what the tool does, the second adds a crucial precondition. Ideal length for this tool.

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 description covers the main purpose, search targets, and precondition. It does not describe the output format in detail, but for a simple search tool with two parameters, the information is adequate. The list of moment types provides sufficient completeness.

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%, so baseline is 3. The description adds value with query examples ('docker compose command') and clarifies the 'id' parameter as a job id from a completed job, enhancing understanding beyond the schema.

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 verb 'search/find' and the resource 'processed video moments'. It lists the types of moments (timestamped transcript lines, on-screen text, scene descriptions), and the precondition 'Job must be done' distinguishes from sibling tools like klaket_get_result or klaket_job_status.

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 requires the job to be 'done', providing a clear precondition. Although it doesn't name sibling tools, the context implies when to use this tool (after processing) vs. alternatives (e.g., check status first). The guidance is clear but could be more explicit about alternatives.

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