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, and it discloses nothing about side effects, input requirements, edge cases, or return format. An agent cannot even tell whether this is a read-only check or what it produces.

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 only 4 words, but this is under-specification rather than conciseness. The words merely repeat the tool name and do not earn their place by conveying any operational information.

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 an empty schema, no annotations, and no output schema, the description was the only vehicle to explain purpose, input mechanism, and return behavior, and it fails entirely. There is nothing here that would let an agent invoke this tool correctly.

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?

Although the schema has 0 parameters (which normally sets a baseline of 4), the tool name implies it needs input such as a text body and a search substring, yet neither schema nor description explains how input is supplied. The description adds zero semantic value about inputs.

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 'Line Contains: Line Contains' is a pure tautology that restates the tool name with a colon and adds no verb, resource, or scope. It provides no differentiation from dozens of similar siblings like x402-grep-lines, x402-contains-any, or x402-first-n-lines.

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 contains no guidance whatsoever about when to use this tool versus alternatives. It is not misleading, but it is entirely silent on selection criteria, prerequisites, or context, leaving the agent with nothing to route on.

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