run_transform_map

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a write operation that is not destructive. The description adds the WRITE_ENABLED requirement, which is useful. However, it does not disclose whether the tool is idempotent (idempotentHint=false is provided but not explained), what happens on repeated execution, or if it can partially fail. Some behavioral gaps remain.

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, efficient sentence that conveys the main action and a key prerequisite. It is front-loaded with the essential verb and resource, and every word adds value. No extraneous content.

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 absence of an output schema, the description should explain what the tool returns (e.g., success status, loaded record count, or error details) and provide more context on side effects or execution behavior. The description only mentions 'load data' without specifying outcomes or potential failures, which is insufficient for a complex transformation 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?

Schema coverage is 100%, and the parameter descriptions in the schema are clear. The description adds no additional meaning beyond the schema, so it meets the baseline expectation but does not enhance understanding of 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 action ('Execute a Transform Map'), the resource ('Import Set'), and the goal ('to load data'). It distinguishes from sibling tools by specifying a unique operation not duplicated elsewhere, and includes a critical prerequisite (WRITE_ENABLED=true). This provides a precise and unambiguous purpose.

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 includes a clear requirement (WRITE_ENABLED=true) that guides when the tool can be used. However, it does not explicitly state when to use this tool versus alternatives (e.g., import_cmdb_data) or when not to use it. The context is sufficient but lacks exclusionary guidance.

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