get_gps_rescue_initial_climb

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

No annotations are provided, so the description carries the burden. It identifies the tool as a getter (read operation) but does not disclose any additional behavioral traits such as side effects, permissions, or rate limits. The description is adequate for a simple read operation.

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 extremely concise: two sentences plus a range specification. Every sentence provides essential information without waste. The structure is clear and front-loaded with the tool's 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?

Given that the tool has no parameters and no output schema, the description is fully complete. It explains what the tool gets, what the value represents, and its constraints. There is no missing information needed for correct invocation.

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 adds value beyond the input schema (which has no parameters) by explaining the meaning of the returned value: 'Altitude to climb...' and providing the data type, range, and default. This helps the agent understand what the tool outputs.

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 that the tool gets the gps_rescue_initial_climb parameter, describing it as 'Altitude to climb from current position before heading home.' It provides a specific verb+resource pairing and distinguishes itself from sibling tools by explaining the parameter's role.

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 implies usage by advising to set 'high enough to clear local obstacles,' which suggests the tool is used to read the current value for evaluation. However, it does not explicitly state when to use this tool versus alternatives like set_gps_rescue_initial_climb or other getters.

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