grep

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

With no annotations, the description carries the full burden of disclosing behavior. It adds only 'by page' and 'exact' context, but does not mention read-only nature, pagination, result format, case sensitivity, or document filtering. This is insufficient for safe invocation.

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, efficient sentence with no redundant words. It front-loads the action ('Find') and specifies scope ('by page'), earning its place without excess.

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 tool with 5 parameters, no schema descriptions, and no annotations, the description is drastically incomplete. It omits key behavioral details like case sensitivity, result limits, document scoping, and return structure. The presence of an output schema does not compensate for this missing invocation guidance.

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 0%, so the description must explain parameters. It only references 'regex' and indirectly 'pattern', leaving the other three parameters (max_results, document_ids, case_sensitive) unexplained. No parameter-level semantics are provided beyond what the schema titles show.

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 finds exact occurrences of registers, fields, signals, addresses, or regex matches by page, using the specific verb 'Find' with named resource types. It does not explicitly differentiate from the sibling tool 'search', but the 'exact' and 'regex' qualifiers provide enough distinction.

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 is given on when to use grep versus alternatives like 'search'. The description implies exact/regex searching but lacks exclusions or comparisons to sibling tools, leaving the agent to infer appropriate usage.

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