rtpengine_stats

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

The description lacks any behavioral details such as idempotency, authentication requirements, or potential side effects. With no annotations provided, the description carries full responsibility and fails to disclose that this is a read-only operation.

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, succinct sentence that immediately conveys the tool's function. It is front-loaded with the key action and resource, with no unnecessary words.

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 description is minimal but acceptable given the existence of an output schema that likely details the statistics returned. However, it does not specify the scope of statistics (e.g., system-wide or per call), leaving some ambiguity.

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 input schema has zero parameters, and the description adds no parameter information beyond what the schema provides. Since schema coverage is 100%, a baseline of 4 is appropriate as no additional parameter semantics are 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 clearly states the action 'Retrieve' and the resource 'RTPEngine media proxy statistics', making the tool's purpose unambiguous. It distinguishes itself from sibling tools like rtpengine_enable or rtpengine_sessions by focusing exclusively on statistics retrieval.

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 or when not to use this tool versus siblings like rtpengine_show or rtpengine_sessions. Given the many rtpengine-related tools, the lack of contextual usage recommendations is a significant gap.

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