get_track_performance

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only describes the return value and does not mention side effects, permissions, rate limits, or any read-only/destructive nature. The description omits essential behavioral context for an otherwise straightforward analysis tool.

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 efficiently conveys the purpose and outputs without any extraneous information. It is front-loaded with the main verb and resource, making it easy to scan.

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?

While the description covers the basic purpose and outputs, it lacks details on error handling, interpretability of web vitals ratings, or any constraints. Given the single parameter and no output schema, the description is minimally adequate but could be more informative for a performance analysis tool.

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 coverage is 100% with one parameter 'url_or_id' that already has a clear description. The tool description does not add any additional semantics beyond that, so it meets the baseline expectation without adding extra value.

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 analyzes performance of a VibeCheck bug report and enumerates the specific outputs: web vitals, navigation timing, and optimization suggestions. The verb 'analyze' and resource 'performance of a VibeCheck bug report' are precise, and the tool distinguishes itself from siblings like analyze_track_errors or get_track by focusing on performance metrics.

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 to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how it compares to sibling tools like get_track or get_track_network. The agent is left to infer usage from the name and description.

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