search_drill_pipe

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

The description aligns with the readOnlyHint annotation by confirming the tool returns data without mutation. It adds context about the data source (NOV Grant Prideco) but does not disclose additional behaviors like result limits, error handling, or authentication requirements.

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 two succinct sentences: first states the action and source, second provides examples and what is returned. No unnecessary words, and the key information is front-loaded.

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 search tool with one parameter and no output schema, the description covers the data source, search type, and return value. It lacks details on pagination, max results, or empty result behavior, but the provided information is adequate for an AI agent to invoke 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?

The description enriches the single 'query' string parameter by providing concrete examples (e.g., 'NC50', '5 S-135'), which the schema lacks. Given 0% schema description coverage, this compensates well, though it could further specify query format or case sensitivity.

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 performs a keyword search over a specific database (NOV Grant Prideco drill string reference), with examples of valid queries, distinguishing it from siblings like get_drill_pipe_specs that fetch by known identifiers rather than searching.

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 provides example queries but does not explicitly state when to use this tool versus sibling tools like get_drill_pipe_specs or list_drill_pipe, nor does it mention any exclusions or prerequisites.

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