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

Annotations only give readOnlyHint=false, destructiveHint=false, openWorldHint=false, but the description discloses a nuanced write policy: read passthrough, a specific allowlisted write pilot gated on client capability, a legacy-client read-only fallback, and hard blocking of dangerous writes. This goes well beyond the annotations and is consistent with them, so there is no contradiction.

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?

Four tightly packed sentences, front-loaded with the core action before the write-policy caveats and routing. Dense with domain jargon (MRTR) but no filler, and each sentence carries distinct information.

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?

An output schema exists, so return values need not be described. For a generic dispatcher with 0% schema coverage, the description compensates reasonably by explaining the write/read policy and explicitly pointing to search for exact schemas, leaving only the parameter-level detail thin.

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 two parameters (name, input) are bare strings/objects, so the description carries the full explanatory burden. It only implies that name identifies a capability and defers real parameter semantics to the sibling search tool, adding little beyond the schema itself.

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 clear verb and resource: 'Execute one OAuth-visible PodMule capability.' The resource is abstract (a named capability) since this is a generic dispatcher, but the description distinguishes itself from the ask_podmule and search siblings by routing ambiguous and schema-lookup needs away. No sibling-confusion remains, though the tool's exact remit is inherently broad.

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?

Explicit when/when-not behavior and alternatives: reads run directly, writes are limited to the allowlisted update_episode pilot on modern MRTR-capable clients, dangerous writes must be done in the PodMule app, ambiguous requests go to ask_podmule, and exact schemas come from search. The routing conditions are spelled out rather than inferred.

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