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

No annotations are supplied, so the description carries the full load. It does disclose the content of the response in useful detail (frames checked, frames with clipping, most pixels, deepest seen, start/middle/end pictures), which is real behavioral context. It omits whether the call is purely read-only, what happens if no run has occurred, and whether the returned pictures are large/expensive.

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?

A single dense sentence that front-loads the resource and then enumerates contents, with no filler. Some of the internal jargon ('the eye's clipping', 'the most pixels, the deepest seen') is terse enough to be slightly ambiguous, but nothing is wasted.

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?

With no output schema, the description usefully supplies the return-field inventory, which is its main value. However, for a tool that depends on a prior run and requires a facts file, it omits preconditions and any failure behavior, leaving an agent to discover the invocation context by trial.

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?

The description never mentions the single 'facts' parameter, but schema description coverage is 100%, so the schema already documents that a gunfacts.json file is required. Baseline 3 applies when the schema does the heavy lifting and the description adds nothing further about the parameter.

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 names the specific resource (the last run's clip report) and enumerates what it contains: frames, per-clip clipping stats, and first-person pictures. That is enough for an agent to know this returns diagnostic data about clipping. It stops short of framing the action as a verb or contrasting itself with the sibling hold_report, which appears to be a parallel report tool.

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?

There is no guidance on when to call this versus hold_report or run_hands, and no mention of prerequisites (e.g., that a prior run must exist for a 'last run' to be reportable). The phrase 'The last run's' is the only usage signal, and it is implicit.

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

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

Without annotations, the description carries the full burden. It helpfully discloses the report's contents and the 'reported, not enforced' nuance for arm angles, but never states that the tool is read-only or that it has no side effects, nor does it mention error behavior when no prior run exists.

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?

A single front-loaded sentence with no filler; each clause maps to a reported field. It is dense with domain jargon but structurally efficient.

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 lists return contents but omits prerequisites (a completed run) and the relationship to run_hands/clip_report. For a report tool with no output schema, this leaves a gap in how to invoke it correctly.

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 single 'facts' parameter is documented in the schema as a Gun Kit facts file. The description adds no parameter-level detail, so baseline 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 resource (the last run's holds) and enumerates the report's contents, which distinguishes it from preset-management siblings. However, it does not explicitly differentiate itself from clip_report, the other report tool, so an agent must infer the choice.

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?

No when-to-use guidance, no prerequisites (e.g., a prior run_hands call), and no mention of clip_report as an alternative. The agent is left to infer that this is the report to call after running hands.

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

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

No annotations are supplied, so the description carries the full disclosure burden, yet it never states that this is a read-only enumeration, what the result set looks like, whether it is paginated, or whether it requires anything of the caller. It only glosses domain vocabulary ('side:mark[:kind]', 'a hand-to-gun pose kept from an approved hold'), which is helpful jargon but not behavioral context.

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?

It is short, but it is a single grammatically broken sentence fragment with no leading verb, so the key fact (what the call does) is not front-loaded. A parenthetical definition interrupts the core statement rather than following it.

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?

With no annotations and no output schema, the description is the only source of truth about the return value, and it describes the data only in a tangled fragment. An agent cannot confidently predict the shape or size of the response before calling.

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?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. The explanation of the 'side:mark[:kind]' hold notation does add useful interpretive meaning for the returned data, though it is not parameter guidance.

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 sentence names the resource ('preset families (pistol, rifle ...)') and its contents (holds, gripped poses), so the domain is inferable, but there is no verb describing the operation – an agent must rely on the tool name to know it performs a listing. No sibling differentiation versus show_preset or set_preset.

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 gives no when-to-use guidance, no prerequisites, and no pointer to alternatives, despite four closely related siblings (show_preset, set_preset, run_hands, hold_report) that an agent could easily confuse with this one.

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

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the Blender/fakepose execution context and a 10-minute time bound, and lists what gets produced. However, it does not clarify mutation semantics: whether existing clips or the blend file are overwritten, whether the operation is idempotent, what happens on failure, or whether Blender must already be running.

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?

It is a single dense sentence that front-loads the core action and execution environment, then lists the concrete outcomes and return value. Every clause adds information and there is no filler.

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 action, environment, time bound, outputs, and return summary, which is useful for a tool with no output schema. For a mutating Blender pipeline with no annotations, however, it omits prerequisites, overwrite behavior, error handling, and the exact nature of the returned summary. It is adequate but has clear gaps.

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 description coverage is 100%, so the schema already documents both parameters. The description implies that the facts file drives the gun configuration and that clips may be selected by default, but it adds no syntax, format, or validation details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific action ('Runs Weapon Lab's Gun Kit hands step with fakepose') and enumerates concrete outputs: gun at aim, preset holds applied, clips keyed/written, eye clipping checked. It does not explicitly name sibling tools or contrast itself with them, but its pipeline-execution purpose is distinguishable from the report/preset siblings.

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?

There is no explicit guidance on when to use this tool versus alternatives such as hold_report or clip_report, nor any stated prerequisites or exclusions. The mention of 'at most 10 minutes' and the default clip behavior gives context, but the agent is left to infer when this step should be run.

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

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

With no annotations, the description must carry the behavioral burden. It usefully discloses overwrite semantics ('adds or replaces') and a downstream coupling to run_hands, but omits permission/validation behavior, error conditions for bad family or hold strings, and whether changes are reversible or persisted across sessions.

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 short sentences, zero filler, with the mutation semantics front-loaded and the runtime consequence second. Nothing could be cut without losing 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?

For a write tool with no annotations, no output schema, and a nested object parameter, the description covers the essential write-and-apply model but leaves out validation behavior, success/failure signaling, and error handling. Adequate for correct invocation but not complete for a mutation.

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 description coverage is 100%, so the baseline is 3: the schema already explains hold format, family enumeration, and the nested preset object. The description adds no parameter-level meaning beyond noting the preset is consumed by the next run_hands.

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 pair and resource: 'Adds or replaces one authored hold,' with the scope narrowed to a single hold. It is distinguishable from list_presets/show_preset by its write semantics, but it never names a sibling and shifts terminology between 'preset' (tool name, param) and 'hold' (description), leaving mild ambiguity.

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 next run_hands uses it' implies the usage context: set this before executing run_hands. However, it gives no explicit when-to-use/when-not guidance, no requirement to inspect with show_preset first, and no note that this mutates stored state versus the read-only siblings.

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

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

With no annotations, the description must carry the full behavioral burden. 'Show' and the detailed return fields imply a read-only inspection operation, but the description does not explicitly state read-only behavior, error handling for missing presets, or any other operational traits.

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 description is a single dense sentence that front-loads the main scope ('One preset in full') and uses the rest to enumerate what is returned. It is efficiently structured, though some domain terms ('mark', 'push out', 'fist') may be opaque without prior context.

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?

There is no output schema, so the description usefully describes the returned preset contents (hand position and digit rules). Combined with the fully documented input schema, an agent has enough to call it correctly, though explicit read-only/error semantics would make it complete.

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 description coverage is 100%, with both family and hold documented in the schema. The description does not add any parameter-level meaning such as accepted formats or enum expansion, so the baseline of 3 is appropriate.

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 states it returns 'One preset in full' and enumerates the concrete contents: hand placement details and each digit's rule. The resource is clear and distinguishes it from list_presets by scope, though it does not explicitly name the sibling or use a canonical retrieval verb.

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 phrase 'One preset in full' implies this is for inspecting a single preset in detail when the summary from list_presets is insufficient. However, there is no explicit when-to-use guidance or mention of alternatives/exclusions.

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