List JobScout sources

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context about the content of the output (providers, authentication boundaries, state), which is useful but does not detail any additional behavioral traits like response format or rate limits. This adds some value beyond annotations, but not extensively.

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, well-structured sentence that front-loads the action ('Show') and immediately specifies the object. It contains no superfluous words and is highly concise.

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 low complexity (no parameters, no output schema), the description is largely sufficient. It conveys the purpose and the types of information returned. However, it does not specify the exact return structure (e.g., list vs. object), so a slightly richer description could enhance completeness.

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 has zero parameters, so the baseline is 4. There is no parameter information needed, and the description does not need to compensate for any schema gaps 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 clearly states the verb 'Show' and the resource 'configured discovery providers', further specifying 'authentication boundaries and enabled state'. This distinguishes it from sibling tools like jobscout_search_jobs and jobscout_deduplicate, which serve different purposes.

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 usage when one needs to view discovery providers, but it does not explicitly state when to use it versus alternatives or provide exclusions. While the purpose is clear, there is no explicit guidance on tool selection, so it falls short of 'clear context, no exclusions' (4).

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