List JobScout sources

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds valuable context about what data is shown (providers, auth boundaries, enabled state, external sites), which goes beyond the annotations and gives the agent a clear expectation of the tool's output.

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 a single, tightly focused sentence that front-loads the main action ('Show') and then enumerates the specific elements returned. Every word contributes to the meaning, with no redundancy or extraneous detail.

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?

Given the tool's simplicity (no parameters, no output schema, clear read-only intent), the description sufficiently covers what the tool does and what it returns. It includes details that help the agent understand the contents of the list, and the sibling names in the context reinforce its distinct role.

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 input schema has zero parameters, so the schema fully covers the parameter space. Per the rubric, the baseline for 0 params is 4; the description does not need to explain any parameter semantics since there are none.

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 uses the specific verb 'show' and identifies the resource as 'configured discovery providers', listing the exact details returned (authentication boundaries, enabled state, external sites). This clearly distinguishes it from sibling tools focused on job search, classification, and deduplication.

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?

The description implies this tool is for viewing sources, but it does not explicitly state when to use it versus the sibling tools, nor does it mention any exclusions or alternatives. The intended usage is inferable from the purpose, but the description provides no direct guidance.

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