get_gps_nmea_custom_commands

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

No annotations are provided, so the description must fully disclose behavior. It only states it's a getter (reading custom commands) but does not mention any requirements (e.g., connected flight controller), side effects, or return structure.

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 short but contains the redundant tool name prefix and unnecessary type info ('[UINT8, default: —]') that does not correspond to any parameter. It could be more concise without the extraneous detail.

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 no output schema and no annotations, the description is insufficient. It fails to explain what the custom commands are used for, how they are formatted in the response, or any prerequisites for invoking the tool.

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 no parameters, so the description does not need to add parameter info. However, it includes the irrelevant text '[UINT8, default: —]' which is confusing and may mislead. A score of 3 is baseline for no-parameter tools.

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 it retrieves custom NMEA sentences for GPS module initialization, specifying it's for NMEA provider only, which distinguishes it from many sibling get_gps_* tools. However, it doesn't specify the format of the returned data (e.g., list of strings).

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 only hints at usage context ('NMEA provider only') but provides no explicit guidance on when to use this tool vs alternatives like get_gps_data or when not to use it. No comparison with sibling tools.

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