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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: an interactive clickable grid on MCP Apps hosts versus a markdown table elsewhere, which tells the agent what actually happens at call time.

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 tight sentences, front-loaded with the picker purpose before the rendering detail. The final query sentence adds little since it duplicates the schema, but nothing is padded.

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?

With no output schema, the description correctly explains the return surface (clickable grid vs markdown table), which is the key thing an agent needs. It is only incomplete on the undocumented 'limit' parameter.

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 only 50%: 'query' is documented (and the description merely restates 'title/host filter'), while 'limit' (default 12, max 40) has no description anywhere and is never mentioned in the description. With low coverage the description should compensate but does not.

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 a specific verb ('Open') and resource ('interactive episode picker') with the user-facing goal of picking an episode to read. It is distinguishable from siblings like list_episodes/search_episodes by its interactive-picker framing, but it never explicitly names or contrasts with those alternatives.

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?

Usage is implied ('for the user to pick an episode to read'), and it usefully notes the host-dependent fallback. However, it gives no explicit when-to-use/when-not guidance and does not route the agent away from list_episodes or search_episodes for the same intent.

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