List all NOV Grant Prideco drill string items in the reference DB (drill pipe, heavy-weight drill pipe HWDP, drill collars) with id, label, product_type, connection, grade.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true. Description adds context about the reference DB and specific fields returned, which is useful beyond annotations.
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?
Single sentence, no wasted words, clearly communicates the tool's action.
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 read-only list with no parameters, the description is complete. Could mention ordering or count, but not essential.
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?
No parameters, so schema coverage is 100%. Description adds meaning by listing output fields, which is useful but not required.
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 lists NOV Grant Prideco drill string items with specific types and fields. It distinguishes from search_drill_pipe which likely implies filtering.
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 purpose is clear and implies use when wanting all items. Sibling search_drill_pipe suggests alternative for searching. Some explicit guidance could improve, but current is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct, but there is potential confusion between get_product_specs (product lines) and get_drill_pipe_specs (drill pipe items), as well as between list_drill_pipe and search_drill_pipe. However, descriptions clarify these differences.
All tool names follow a consistent verb_noun pattern in snake_case (get_, list_, search_, submit_), making it predictable for agents.
12 tools cover two main domains (FEODE company and drill string reference) without excess or deficiency, providing a well-scoped set.
The tool surface covers key operations for both domains: company info, product/service lifecycle, and drill string reference. Minor gaps like lack of company news or additional equipment categories, but core workflows are supported.