get_telemetry_names

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

No annotations are supplied, and the description fails to disclose any behavioral traits such as whether the call is safe, idempotent, or has side effects. The return type is mentioned but is already evident from the output schema.

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 short, but it is under-specified rather than concise. It lacks valuable information that could be included without adding significant length.

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 tool's simplicity (zero parameters, output schema present), the description is still incomplete. It does not clarify the nature of the telemetry names (e.g., available metrics, channels, or sensors) which would aid in using the tool effectively.

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 baseline is 4 per instructions. The description adds no additional parameter information, but none is needed since the schema already covers it fully.

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 'get telemetry names' is essentially a tautology, restating the tool name without elaborating on what telemetry names are or how they are used. It does not differentiate from sibling tool 'get_telemetry_values', leaving ambiguity about what exactly is returned.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks any contextual information about prerequisites or typical use cases.

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