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

The annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a useful precondition to check capabilities/schema and shows an example, but it does not disclose rate limits, auth requirements, pagination, error behavior, or freshness implications beyond the schema.

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 concise and front-loads the main instruction before the example and guide URI. The embedded JSON example is useful but makes the sentence structure less clean; overall there is little wasted wording.

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?

For a complex multi-source dispatcher with four parameters and 0% schema description coverage, the description is very thin and relies heavily on external capabilities/schema and a guide URI. The output schema removes the need to explain return values, but input semantics are not sufficiently covered.

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%, so the description must carry parameter meaning. It provides one example using source, operation, and params, but does not explain the 24 enum values for source, the operation string format, the params object contents, or the freshness enum, leaving most parameter semantics undocumented.

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 identifies a generic dispatcher for 'advanced source operations,' but it does not specify what those operations concretely do or what resource scope they cover. It distinguishes itself from dedicated tools for common tasks, but the core purpose remains broad and escape-hatch-like.

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?

It explicitly says to check capabilities/schema first and directs common tasks to dedicated tools, giving clear context for when this tool is appropriate. It stops short of naming specific sibling alternatives or source-specific exclusions, but the usage boundary is reasonably clear.

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