robot_status

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

No annotations are provided, so the description must stand alone. It states the tool reads status, GPS, and telemetry, implying a non-destructive operation, but provides no detail on return format, internal behavior, or error conditions. This is adequate for a read-only convenience tool but lacks depth beyond the basic function.

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, immediately front-loading the key information ('read status, GPS and telemetry') and the convenience angle. Every word earns its place without redundancy or unnecessary detail, 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?

The tool is simple (zero parameters, no output schema), but while the description states what is read, it does not clarify the structure of the result or whether it aggregates data from multiple sources. This leaves some ambiguity for an agent trying to interpret the response, though it is sufficient for a basic status fetch.

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 zero parameters, so the schema trivially covers everything. The baseline for zero parameters is 4, and the description adds no parameter-specific meaning because none exist. This meets expectations without needing further elaboration.

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 uses the specific verb 'read' and clearly names the resources: status, GPS, and telemetry. The term 'Convenience' differentiates it from sibling tools like read_topic by indicating this is an aggregate one-call operation, making its purpose distinct and unambiguous.

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?

Usage guidance is implied rather than explicit. 'Convenience' and 'in one call' suggest using this tool when multiple data types are needed at once, but no explicit alternatives are excluded. Sibling tools like read_topic or list_topics are not mentioned, or when not to use this tool.

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