get_performance_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. It only states that the tool gets metrics and statistics, but does not mention whether it is read-only, whether it requires an active browser session, what specific metrics are returned, or any potential side effects. For a tool with no annotations, this is insufficient.

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 sentence that immediately states the action ('Get') and the target ('server performance metrics and statistics'). It contains no filler words and is fully front-loaded. Every word contributes to understanding, making it highly concise and 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?

Given the tool's simplicity (no required parameters, no nested objects, no output schema), the description is minimally adequate but lacks detail about what specific metrics are included or how the output is formatted. Since there is no output schema, the description should provide some overview of return values; 'metrics and statistics' is too vague to be fully complete.

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 schema has a single dummy parameter with a clear description ('Dummy parameter for no-parameter tools'), and schema coverage is 100%. The description adds no further parameter explanation, but the schema alone is sufficient because the parameter is a placeholder and requires no semantic enrichment. Baseline 3 is appropriate.

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 tool's function: getting performance metrics and statistics. The verb 'Get' is specific, the resource 'Browser[X]MCP server performance metrics and statistics' is clear, and it is distinguished from all sibling tools which focus on navigation, interaction, and element inspection. No ambiguity exists about what this tool does.

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 does not explicitly state when to use this tool versus alternatives, but the name and content imply it is for retrieving server performance information. There are no sibling tools that offer similar functionality, so context is implicit rather than explicitly guided. This falls into 'implied usage'.

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