location

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

With no annotations provided, the description carries the full burden. It discloses that the tool does not transmit and only affects the session, which are key behavioral traits. It does not detail error handling or permissions, but for a simple override, this is adequate.

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 concise with three sentences, each adding value. It front-loads the purpose and avoids redundancy. No unnecessary details.

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 simple tool with two parameters and no output schema, the description covers purpose, behavior, and usage context. It lacks explanation of the 'instance' parameter and does not specify return values or error conditions, but overall it is sufficient.

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 no descriptions (0% coverage). The description partially compensates by explaining the 'grid' parameter format ('4- or 6-character'). However, the 'instance' parameter is not described, leaving ambiguity.

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 overrides the session Maidenhead grid, with specific verb ('Override') and resource ('session Maidenhead grid'). It also distinguishes from siblings by noting 'No transmit', which differentiates it from the transmit tool.

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 specifies when to use ('Intended for mobile/portable operation where the grid changes during a session') and implies when not to use ('Session-lifetime only — does not change the persistent setting'). However, it does not explicitly mention alternative tools for persistent changes, such as 'configure'.

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