import_sources

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

With no annotations, the description must carry the burden of behavioral disclosure. It states that the tool returns a list but does not mention that it is a read-only operation, whether authentication is required, or any potential side effects or errors. The behavior is mostly implied by the verb 'Get' and the static list, but the lack of explicit disclosure leaves a gap.

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 sentence that front-loads the action and then provides a comprehensive enumeration of sources and types. While the list is long, it is necessary to convey the exact values an agent can expect. No fluff or redundancy.

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 discovery tool with one optional parameter and no output schema, the description fully covers what it returns and the scope. There is nothing an agent needs to know beyond the listed values to decide whether to call this tool.

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 only parameter, companyId, is fully documented in the schema with a clear description. The tool description does not add any additional meaning beyond the schema, which is appropriate given 100% schema coverage. Baseline 3 is correct.

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 states a clear verb ('Get') and resource ('available import sources and import types'), and it enumerates the specific sources and types returned. This precisely distinguishes it from sibling import tools like import_execute or import_upload, which perform actions rather than list options.

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 implicitly conveys that this tool is for discovering available sources and types before performing an import, but it does not explicitly say 'use this to prepare for import_execute' or mention any when-not-to-use conditions. No alternatives are named, so the guidance is implied rather than stated.

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