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

Annotations already declare read-only and idempotent behavior. The description adds value by specifying the type of data (latency, throughput, artifact status) but does not discuss other behavioral aspects like rate limits or return format. This is acceptable given the strong annotation coverage.

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 front-loads the usage condition. It is concise and free of fluff, but could be improved by briefly noting the optional view parameter.

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?

For a simple tool with one parameter and annotations, the description covers the tool's purpose and main output. However, it omits explanation of the 'view' parameter and does not describe return values (output schema missing), so agents may not know how to adjust the view or what to expect.

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 sole parameter 'view' has an enum (summary/full) but no description in the schema (0% coverage). The tool description does not explain the parameter's purpose or difference between views, leaving the agent without guidance on how to use it. Description fails to compensate for missing schema documentation.

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 provides measured latency, throughput, and visibility artifact status for SEAR, identifying the verb (retrieve/show) and resource (benchmarks). It distinguishes from siblings by focusing on benchmark data versus help or overview.

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 starts with 'Use this when you need...', giving explicit context for when to use. However, it does not mention when not to use or suggest alternatives like sear_overview for broader information, so it lacks exclusions.

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