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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic function and does not mention authentication requirements (e.g., 'x-hapi-auth-state'), response structure, error scenarios, or any side effects. The 'get' verb implies a read operation, but no further behavioral details are provided.

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 sentence with no wasted words, but it is under-specified for a 2-param tool. It is concise but not appropriately sized to convey necessary usage details. The structure is simple and front-loaded, but the brevity trades off clarity.

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 lacks an output schema and annotations, and the description provides minimal context. It does not explain the frontmatter fields, the guest parameter format, or how this metadata differs from other endpoints. Given the sibling tool set, more context is needed to know when and how to invoke this tool correctly.

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 0%, and the description does not compensate. It does not explain what 'guest' refers to (name, ID, slug?) or the purpose of 'x-hapi-auth-state'. The parameter semantics are entirely absent from the description, leaving the agent to guess from the parameter names alone.

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 action ('Get') and the resource ('episode metadata') with a specific output format ('JSON (frontmatter)'). It distinguishes from sibling tools like getEpisodesGuest (likely returns guest info) and getEpisodesGuestTranscriptformat (transcript) by specifying the metadata-as-JSON scope.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies usage when needing episode metadata in JSON format, but there are no explicit exclusions, prerequisites, or comparisons with sibling tools.

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