katto_get_job

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds significant context: clip ordering by virality score, the hd=false nuance (URL works, 1080p still rendering), hd_ready flag semantics, and 404 on unknown id. This goes well beyond the structured metadata.

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?

The first sentence states the core purpose, and each subsequent sentence adds necessary behavioral nuance without fluff. The length is justified by the semantic complexity of the hd and hd_ready flags, and the error behavior is clearly front-loaded after the main description.

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?

Despite no output schema, the description fully specifies the returned clip fields, ranking order, status semantics, hd behavior, and error handling. An agent can correctly invoke the tool and interpret its results without any missing essential information.

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% and the only parameter id is already described as coming from katto_create_clip_job. The description adds no further parameter-level details beyond 'by id' and the 404 behavior, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Get the status, progress and clips of a job by id.' This clearly identifies the tool's function and the id parameter, distinguishing it from listing tools like katto_list_jobs and the clip-focused katto_get_clips.

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 implies usage by mentioning the job id from katto_create_clip_job and the 404 for unknown ids, but it never explicitly states when to use this tool over siblings like katto_get_clips or katto_list_jobs. There are no when-not or alternative routing cues.

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