analyze_performance

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

No annotations are provided, so the description carries the full burden. It reveals only that metrics are 'basic,' with no disclosure of what is measured (load time, Core Web Vitals, page weight), whether the target must be publicly reachable, or any auth/rate-limit behavior.

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?

A single short sentence with no wasted words, but it is under-specified rather than genuinely concise. There is room to add scope and usage detail without bloat.

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 annotations, no output schema, and no parameter documentation, the description is too thin for a tool whose output and scope ('basic' vs comprehensive performance data) are undefined. An agent cannot predict what it gets back or when it applies.

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?

One parameter at 0% schema description coverage, and the description adds nothing about the url beyond what the schema's 'format: uri' already conveys. It should clarify expectations such as a publicly reachable URL or whether redirects are followed.

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 specific verb (Analyze) and resource (page performance metrics), which distinguishes it from most siblings like analyze_title or analyze_meta. However, it does not differentiate from adjacent ambiguous siblings such as analyze_technical, analyze_mobile, or analyze_website, and 'basic' is vague about scope.

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 indication of when to use this tool versus the many sibling analyzers. An agent must infer that performance is a distinct concern from technical/mobile/accessibility analyses, with no explicit routing or prerequisites given.

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