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

No annotations are provided, so the description carries the full burden. It discloses the key behavior of applying AS 39.27.020 geographic differential, which is valuable context. However, it does not specify the return format (e.g., annual salary vs. hourly) or any error conditions.

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 sentence that front-loads the official status and core function. Every phrase adds value, with no redundant or filler content.

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 lookup tool, the description covers the main inputs and the special differential, making it largely complete. However, without an output schema, it would benefit from stating the return format explicitly.

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 description references all three parameters without adding significant new syntax or format details. It repeats the parameter names but does not clarify formats beyond the schema examples.

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 returns official GG-schedule pay based on range, step, and duty station, with Alaska's statutory geographic differential. This specific terminology distinguishes it from siblings like get_salary_data, which may be broader or less specialized.

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 for Alaska GG-schedule salary lookups, providing clear context that the tool is for obtaining pay with a range/step/duty station combination. However, it does not explicitly mention when not to use it or compare it to alternate tools like get_salary_data.

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