Get any resource

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

With no annotations provided, the description carries the full safety burden. 'Read' clearly signals a non-mutating operation, which is helpful, but the description doesn't disclose likely errors, required cluster permissions, behavior for missing resources, or how the response is shaped. It is adequate but not transparent about failure or edge-case behavior.

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 one compact sentence that states the operation, resource class, and identifying keys, with an immediate illustrative example. Every word earns its place and nothing is redundant.

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?

The tool is a generic Kubernetes object reader with no output schema and no annotations. The description and schema cover the five parameters well, but the description does not detail response format, namespace omission for cluster-scoped resources, or any operational caveats. It is sufficient for a basic call but not fully complete for an unfamiliar agent.

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 100%, so the input schema already documents all parameters. The description adds small value with examples like 'apiVersion=apps/v1, kind=Deployment', but it does not materially expand on the schema definitions.

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 uses a specific verb ('Read') and resource class ('arbitrary Kubernetes object') with the required identifying tuple (apiVersion/kind/name). It clearly differentiates itself from the sibling get_pod/list_* tools by emphasizing arbitrary resource access rather than a specific type.

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 word 'arbitrary' implies this tool is for resources without a dedicated sibling tool, but the description never explicitly says when to prefer get_resource over get_pod or list_deployments. Usage context is implied rather than stated, and no exclusions or fallback guidance are provided.

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