get_recording_storage

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

With no annotations, the description carries the full behavioral disclosure burden. It states that it 'Returns disk usage information', implying a read-only operation, but lacks details about aggregation, units, or whether it modifies anything. The behavior 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?

The description is two short sentences and fairly efficient. The second sentence repeats 'recording storage' and adds little value, but overall it is concise and front-loaded with the main purpose.

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 simple zero-parameter read-only getter, the description is adequate. It names the resource and return type, and an output schema exists to provide detailed return structure. However, it does not clarify whether 'across all cameras' implies an aggregate or per-camera breakdown.

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 has zero parameters with an empty input schema, so parameter semantics are trivial. The description correctly avoids mentioning any parameters, which is appropriate given the 100% schema coverage and absence of parameters.

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 uses the specific verb 'Get' and identifies the resource as 'recording storage usage across all cameras', making the scope clear and distinguishing it from sibling tools like get_recordings or get_stats.

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 explicit guidance is provided on when to use this tool versus alternatives like get_stats or get_recording_summary. Usage is implied by the tool name and description, but no exclusions or alternative mentions are included.

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