show_importdetails

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

No annotations provided, so the description carries the behavioral disclosure burden. 'Get import definition metadata' clearly indicates a read operation with no side effects. However, it does not mention permissions, error conditions, or output details beyond listing included fields. Adequate but minimal.

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 concise sentences: the first states the action and scope, the second provides usage guidance. No redundant words or irrelevant details. Every sentence adds value.

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 is a metadata retrieval with 3 parameters and no output schema, the description covers the key purpose and usage context. It mentions the included data (source file, column mapping) and provides a practical tip. Could be enhanced by noting the output format or error cases, but it is sufficient for the agent.

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?

Input schema has 100% description coverage; each parameter is described as 'ID or name'. The description does not add any additional meaning or constraints beyond the schema. Baseline of 3 is appropriate since the schema already documents the parameters.

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 tool retrieves import definition metadata including source file and column mapping. It distinguishes from siblings like run_import by explicitly advising 'Check this before run_import'. The verb 'get' combined with 'metadata' makes the purpose 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?

The description provides clear usage context: 'Check this before run_import to understand the expected data format.' This tells the agent when to use this tool and implies not to use it for execution (use run_import instead). It does not explicitly exclude other scenarios, but the guidance is helpful.

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