get_metrics

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. 'Real-time' hints at temporal behavior but reveals nothing about side effects, data scoping, rate limits, authentication, or return format. This is completely insufficient for a tool with no other metadata.

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 two-word description is extremely short, but this is under-specification rather than effective conciseness. It omits all substantive information and does not earn its place as a useful description.

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?

With no output schema and no annotations, the description is the only source of context. It does not explain what 'metrics' means, what the return structure looks like, or what 'real-time' implies operationally. The tool is effectively opaque to an agent.

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, making the schema coverage trivially 100%. Per the rubric, 0 params yields a baseline of 4, and the description does not need to add parameter semantics because there are none.

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 'Real-time Metrics' essentially restates the tool name 'get_metrics' without a verb or specific resource. It vaguely suggests the tool returns metrics in real time but provides no detail on what metrics or how this differs from sibling tools like tcai_metrics or get_system_status.

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 versus alternatives. The description is a noun phrase with no context, prerequisites, or exclusions, leaving the agent without any basis for selecting this tool over its siblings.

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