getPerformanceMetrics

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Get performance metrics' without revealing whether it actively loads a URL, monitors over the duration, requires prior SDK setup, or has side effects. The metrics and duration parameters imply ongoing collection, but that behavior is not stated.

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?

Single sentence, front-loaded with the action and object, with no filler. It is appropriately terse, though brevity comes at the cost of important behavioral context. The structure is clean and immediately scannable.

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?

No output schema and no annotations exist, so the description must explain invocation context and return behavior. It omits return format, prerequisites such as installMantisSDK or validateSetup, and how url and duration affect monitoring. For a tool with three parameters, this is too sparse to support confident invocation.

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?

Schema description coverage is 100%, so the schema already documents the URL, metric list, and duration semantics. The tool description adds no additional parameter meaning beyond restating the general purpose. Since the schema handles parameter documentation, the 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?

States a clear verb+resource: retrieves performance metrics for a 3D experience. It is distinct from all sibling tools, which focus on SDK setup, events, store management, and debugging. Though somewhat generic, it is not tautological or misleading.

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 explicit guidance about when to use this tool versus alternatives, and no prerequisites are mentioned. There are no sibling performance tools, so intended usage is implied only by naming and context. It does not state whether it should be called after setup, during development, or in a specific environment.

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