get_oke_node_pool

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

With no annotations provided, the description carries the full burden. It clearly indicates a read-only operation ('Get detailed information'), which is appropriate. However, it doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or whether the operation is idempotent. The return details are listed but lack context on format or potential omissions.

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 well-structured and front-loaded with the core purpose. It uses bullet points efficiently to detail return values without unnecessary elaboration. Every sentence earns its place, and there's no redundant or verbose content.

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?

Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description is reasonably complete. It covers purpose, parameter semantics, and return details. However, it lacks information on authentication, error handling, or operational constraints, which would enhance completeness for a cloud resource tool.

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 adds meaningful context for the single parameter: 'node_pool_id: OCID of the node pool.' This clarifies the parameter's purpose and format (OCID), which is valuable since schema description coverage is 0%. However, it doesn't provide examples or validation rules beyond the basic definition.

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's purpose: 'Get detailed information about a specific node pool.' It specifies the verb ('Get') and resource ('node pool'), and distinguishes it from sibling tools like 'list_oke_node_pools' by focusing on a specific instance rather than listing multiple.

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 usage context by specifying 'a specific node pool' and providing the required 'node_pool_id' parameter. It differentiates from 'list_oke_node_pools' by focusing on detailed retrieval vs. listing. However, it lacks explicit when-not-to-use guidance or alternative tool mentions beyond this implicit distinction.

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