get_actual_sample_depth

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses one meaningful behavior: the actual depth can be less than configured. It does not mention behavior before any capture, error conditions, or return format, but for a simple getter this is minimally transparent.

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 delivers the core meaning and a useful caveat without redundancy. Every word earns its place.

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 zero-parameter getter, the description is nearly complete: it names the value and its important property. Minor gaps remain around return units and behavior when no capture has occurred, but these are not severe for such a simple tool.

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, and the schema confirms an empty properties object. Therefore no parameter documentation is needed; the baseline for zero-parameter tools 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 clearly identifies the resource (actual sample depth of the last capture) and the key qualifier that it may be below the configured value. It does not use an explicit verb like 'gets', but the noun phrase is unambiguous and separates this from configured-depth and sibling getters.

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 'of the last capture' implies the tool should be used after a capture to inspect measured depth, and 'may be less than configured' hints at comparing against set_sample_depth. However, no explicit when-to-use guidance or alternatives are named, so usage is implied rather than stated.

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