get_mcp_telemetry

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read operation via 'Obtiene' but says nothing about permissions, side effects, rate limits, or the operational context (e.g., mcp_bridge) beyond a terse mention.

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 front-loaded sentence with no wasted words. However, it is so minimal that it fails to carry its share of information for a tool with a parameter and no annotations, bordering on under-specification rather than efficient conciseness.

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?

An output schema exists, so return values need not be explained. Still, the description omits parameter semantics, usage context, and behavioral details, making it incomplete for an agent trying to invoke the tool correctly under ambiguous 'telemetry' semantics.

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 single parameter 'printer' has 0% schema description coverage and is not mentioned or explained in the description. The description does nothing to compensate for the missing parameter semantics, leaving the agent without guidance on what values are valid or what 'default' means.

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 states a verb ('Obtiene') and a resource ('telemetría de extras MCP (mcp_bridge)'), so the general purpose is identifiable. However, 'telemetría' is vague and no sibling differentiation is provided, leaving the agent unsure how this differs from related tools like get_server_info or get_klippy_log.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. The description only asserts what it retrieves, not the context in which retrieval is appropriate.

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