squire

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

With no annotations, description carries full burden and discloses key traits: 'disposable' implies temporary/isolated execution, 'ffmpeg installed' declares dependencies, and 'optionally download' clarifies persistence behavior. However, it omits critical execution details like timeout enforcement behavior, cleanup guarantees for undownloaded files, or security boundaries.

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 ~20 words with zero waste. Information is front-loaded ('Run Python media jobs'), followed by environment constraints ('disposable remote runtime with ffmpeg'), and closes with side effects ('optionally download').

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?

For a 5-parameter remote execution tool without output schema or annotations, description adequately covers the job lifecycle (execution environment, optional artifact retrieval). Minor gaps remain regarding return value structure and failure modes, but sufficient for tool selection.

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%, establishing baseline 3. Description adds semantic value by mapping 'Python media jobs' to the required 'script' parameter and clarifying that 'download_artifacts_dir' corresponds to generated artifacts from the job, connecting the high-level operation to specific schema elements.

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 provides specific verb ('Run') with clear resource type ('Python media jobs'), environment context ('disposable remote runtime with ffmpeg'), and implicitly distinguishes from siblings like 'compile', 'build', or 'data' via the 'ffmpeg' and 'media' specificity.

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?

Provides implied usage context through 'ffmpeg installed' (suggests media processing workloads) and 'optionally download' (indicates persistence choice), but lacks explicit guidance on when to prefer this over 'data' or 'compile' siblings, or prerequisites.

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