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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact — the payload is identical to GET /api/ai/sources, implying stable, cacheable content — but says nothing about payload size, freshness, or whether the data is static config versus live citations.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity is partly under-specification rather than compression of genuinely dense content.

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?

There is no output schema, so the description carries the entire burden of explaining what comes back, and "sources map" does not convey the shape, keys, or contents of the payload. For a retrieval tool whose only value is its return data, that is a material gap.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; baseline 4 applies. additionalProperties=false confirms no hidden arguments are expected.

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?

"Returns the AssurancesLabs citation-oriented sources map" gives a verb and a named resource, so the agent knows this is a read of a sources payload. However, "sources map" is never unpacked — what the entries represent (citation URLs, publishers, IDs?) is left entirely implicit. The sibling resolve_quote_intent is not referenced, so differentiation must be inferred from names alone.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the one sibling. An agent cannot tell from this text whether the tool is a prerequisite for resolve_quote_intent, a discovery step, or an independent lookup.

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