get_gimbal_position

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves current position with human-readable directions, implying a read-only operation that returns formatted data. However, it doesn't cover critical aspects like whether this requires specific permissions, latency/rate limits, error conditions (e.g., if camera is offline), or if the data is real-time vs. cached. For a tool with zero annotation coverage, this is a significant gap.

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, efficient sentence that front-loads the core purpose ('Get current camera gimbal position') and adds clarifying details ('pan, tilt, zoom' and 'human-readable directions') without any wasted words. Every part earns its place, making it highly concise and well-structured.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It covers the basic purpose and output format, which is sufficient for a simple read operation. However, without annotations or output schema, it should ideally mention more behavioral aspects (e.g., real-time nature, potential errors) to be fully complete. It meets the minimum viable standard but could be improved.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds value by specifying what data is returned (pan, tilt, zoom) and the format (human-readable directions), which goes beyond the schema. Since there are no parameters, the baseline is 4, and the description provides useful output context.

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 states the tool's purpose: 'Get current camera gimbal position (pan, tilt, zoom) with human-readable directions.' It specifies the verb ('Get'), resource ('camera gimbal position'), and output format ('human-readable directions'), distinguishing it from siblings like control_gimbal (which likely sets position) and take_snapshot (which captures images). However, it doesn't explicitly differentiate from check_system_status, which might include similar data, so it's not a perfect 5.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., camera must be powered on), exclusions (e.g., not for historical data), or comparisons to siblings like check_system_status (which might include gimbal position as part of broader status) or look_and_analyze (which might involve positioning). This leaves the agent to infer usage from the purpose alone.

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