variable_library_get_definition

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

The description adds useful behavioral context beyond the readOnlyHint/destructiveHint annotations by noting the operation is long-running, writes specific files to a local output directory, and returns a list of files written. The local write does not contradict readOnlyHint since it does not mutate the Fabric resource.

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 compact and front-loaded: it states the action and long-running nature first, then gives the concrete side effects and return value. Every sentence contributes useful information with no filler.

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 tool with three simple parameters, no output schema, and read-only annotations, the description covers the essential behavior, output, and side effects well. It could be more complete by explaining how to handle the long-running aspect, such as polling or timeout expectations, but it is sufficient for correct selection and invocation.

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 schema already documents all three parameters adequately. The description reinforces that outputDirectoryPath receives the definition files and lists the expected file names, but it adds little parameter meaning beyond what the schema provides.

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 specific action and resource: getting the definition of a variable library. It also explains the unique behavior of writing definition files to an output directory and returning the written file list, which clearly distinguishes it from variable_library_get and variable_library_update_definition.

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 implies when to use this tool: when a caller needs the full definition files exported to a directory. However, it does not explicitly say to use variable_library_get for simple metadata retrieval or update_definition for modifications, and it offers no exclusions or alternative routing.

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