linode_api_get

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

Discloses that only GET is allowed (matching readOnlyHint annotation), refuses secret-returning endpoints, and scrubs response of secrets. Adds significant behavioral context 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?

Three short sentences, each adding critical information: purpose, allowed method, restrictions. No filler. Front-loaded with key details.

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?

Covers input, restrictions, and security. No output schema, but response scrubbing is noted. Sufficient for an agent to use as a general-purpose escape hatch, though return format is not specified.

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 coverage is 0%, but description explains 'path' as relative v4 path and 'params' as optional query params, with an example. Adds meaning beyond the bare schema, though missing explicit descriptions of each parameter individually.

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?

States it is a read-only escape hatch for GET requests against Linode API v4 paths not covered by curated tools, with examples like '/images' or '/databases/engines'. Clearly distinguishes from sibling tools.

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?

Explicitly allows only GET, requires a relative v4 path and optional params. Mentions that secret-returning endpoints are refused. Implies use when no curated tool exists, but lacks explicit when-not-to-use or alternative suggestions.

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