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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that - invalid args return the expected schema plus an example - but says nothing about auth, rate limits, or per-source failure modes.

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 first sentence is front-loaded and the error-behavior note follows logically. The remaining bulk is a dense, unbroken wall of source:operation pairs that is necessary given the enum-free schema but is hard to scan and would be better structured.

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 no explanation, and the enumeration plus error-recovery note make the tool callable. For a dispatcher this complex, the one real gap is not telling the agent how to discover the per-operation args it must pass.

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 100%, but the schema is effectively empty of meaning: source and operation are free-form strings with no enums and args is an untyped object. The description compensates substantially by enumerating every valid source and its operation names, which is the real semantic content. It still does not explain what args each operation accepts.

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 action (run a source operation with args) and enumerates every source/operation pair, so an agent can see exactly what is invokable. It does not, however, distinguish this dispatcher from siblings like ireland_describe or fetch, leaving the routing decision partly to inference.

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 only implied: the source/operation list tells the agent what can be called, and 'bad args return the expected schema and an example' hints at a discovery-and-retry workflow. There is no explicit when-to-use-this-vs-siblings statement and no pointer to a describe/catalogue tool for learning each operation's args.

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