get_metrics

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

With no annotations, the description carries the full burden of behavioral disclosure, but 'Real-time Metrics' reveals nothing about side effects, permissions, return format, or whether it is read-only. It fails to disclose any behavioral traits beyond a vague temporal attribute.

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 only a two-word fragment. While extremely short, it is under-specified rather than appropriately concise. It lacks a full sentence structure and fails to convey enough information to be considered 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?

With no output schema, no annotations, and a highly ambiguous description, the tool's behavior and return values are unexplained. The sibling list includes several metrics-related tools, further increasing the need for contextual clarity that this description does not provide.

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, and the schema is empty (100% coverage). Per the instructions, a baseline score of 4 applies for 0-param tools. The description adds no parameter-specific meaning, but none is needed.

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' is a noun phrase that essentially restates the tool name 'get_metrics' with the modifier 'real-time'. It does not specify an action (e.g., 'retrieve', 'fetch') and does not distinguish itself from siblings 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?

The description provides no guidance on when to use this tool versus alternatives. There is no indication of preferred contexts, exclusions, or even a hint about what distinguishes 'get_metrics' from other metric-related tools in the sibling list.

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