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

With no annotations, the description must carry the transparency burden. 'Everything known' discloses comprehensive scope, and 'including its honest limits' hints that the tool will report its own limitations. However, it does not specify return format, common error cases, or whether any special permissions are needed. It provides some context but remains vague.

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 entire description is a single short sentence, front-loaded with the key action. It is appropriately terse and contains no filler or repetition.

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 simple read tool with one parameter and no output schema, the description gives a general sense of the return content ('everything known') but does not describe the structure or any limitations. Given the presence of many sibling tools, this level of detail is adequate but not rich; an agent might not know what to do with the returned data without further guidance.

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 description only repeats 'source id' without adding extra meaning. It does not explain what a source id looks like, how to obtain one, or any constraints. The parameter name itself is the only semantic clue, which is insufficient for an agent unfamiliar with the domain.

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 title 'Read one source' and description 'Everything known about one source id' clearly state the tool's purpose: retrieving all available data for a single source. This distinguishes it from siblings like list_sources (which lists many) and request_source (which requests a new source). The verb 'read' and resource 'source' are specific and unambiguous.

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?

No explicit when-to-use guidance or mention of alternatives. However, the title and description imply usage when one needs complete information about a specific source id, contrasting with list_sources. This is implied rather than stated, so it does not fully guide an agent choosing among sibling tools.

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