List FEODE's seven product and service lines with their IDs, names, and categories. Use this to identify the range of offshore oilfield capabilities available.
List FEODE's 7 product/service lines (id, name, category).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, assuring safe read-only operation. The description adds behavioral context: returns exactly 7 lines with specific fields. No mention of performance or auth, but the safety profile is clear from 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?
The description is a single, concise sentence that conveys all necessary information without filler. Every word adds value.
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 list tool with no parameters and annotations providing safety, the description is complete. It specifies the return fields (id, name, category) even without an output schema, and the fixed number 7 sets clear expectations.
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 exist, and schema description coverage is 100% (empty schema). Per guidelines, 0 params baseline is 4. The description adds no parameter info because none exist, so score remains 4.
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 verb 'List' and the resource 'FEODE's 7 product/service lines' with specific fields (id, name, category). This distinguishes it from sibling tools like 'get_product_specs' which likely provide details for one product, and 'search_capabilities' which involves 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 implies use for obtaining an overview of all product lines but provides no explicit guidance on when to use vs alternatives. It does not exclude usage for filtering or detailed specs, leaving some ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.