import_configsource

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

Annotations already mark it as non-read-only and non-idempotent; the description adds that it requires write permission and uses multipart upload. It does not, however, disclose conflict/overwrite implications beyond what the schema parameters hint at, so there is room for more transparency.

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?

Two focused sentences, with the core action and requirement front-loaded and the alternative placement in a single secondary clause. No filler 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?

With only three parameters, full schema coverage, and sibling differentiation, the description is largely complete. A short note on what the import returns or what happens on conflict would close the remaining gap, but nothing needed to select the tool is missing.

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 coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that 'definition' must be in LM Exchange JSON format rather than a REST API definition, which materially affects how the agent should prepare the input.

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?

Description names a specific action and resource: 'Import a ConfigSource from LM Exchange JSON format via multipart upload.' It explicitly contrasts with create_configsource, making the purpose and boundary unmistakable.

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?

Gives an explicit routing rule: use create_configsource for REST API format definitions (e.g., from export_configsource), and notes the write-permission prerequisite. This tells an agent when to pick this tool over the closest sibling.

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