fluent_transform

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

Annotations already include destructiveHint=true and openWorldHint=true, which lowers the bar. The description adds context about authentication and source selection but does not disclose specific side effects (e.g., overwriting existing files or modifying the Fluent project). It doesn't contradict the annotations, but it also doesn't significantly elaborate beyond their safety signals.

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 three sentences long, front-loaded with the primary purpose, then providing actionable usage modes. Every sentence earns its place without redundancy or fluff.

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?

The description covers the main usage modes, authentication requirements, and parameter relationships. Given the tool's complexity (two sources, table hierarchy, optional id), it is fairly complete. It could mention what the output looks like or that conversion writes to the Fluent project directory, but the schema already documents directory and workingDirectory parameters, and there is no output schema to explain.

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 meaningful context beyond the schema by explaining that 'from' is for local files and omitting it pulls from the instance, and that 'table' can be combined with 'id' to target a specific record and its relationships. This goes beyond the raw schema descriptions.

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 uses a specific verb and resource: 'Download and convert XML metadata records from a ServiceNow instance or local path into Fluent source code.' It clearly distinguishes the tool from sibling tools like build_fluent_app or deploy_fluent_app by focusing on transformation of XML metadata into Fluent source.

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?

Provides explicit usage guidance: 'Use from for local XML files, or omit to pull from instance' and 'Use table (SDK v4.7.0+) to transform by table hierarchy, optionally with id.' Also notes the authentication requirement. However, it doesn't explicitly mention alternatives or when not to use this tool in favor of a sibling tool, so it doesn't fully earn a 5.

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