Manage Foundry Folder

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

Despite annotations already indicating destructive hint and open world, the description adds valuable behavioral context: the workflow for using the returned uuid, and the limitation that only freshly-created folder UUIDs are known (requiring structure:read for discovery). This goes beyond what annotations provide.

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 two sentences, front-loaded with the core purpose, and adds a valuable usage note and limitation. Every sentence earns its place with no redundant information.

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 8-parameter schema and no output schema, the description provides enough context for the main workflow and a key limitation. It could mention more about error cases or return format, but the schema covers parameter details, and the description conveys the essential operational flow.

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 description coverage is 100%, so parameters are fully explained in the schema. The description mentions the returned uuid from creation, but doesn't add semantic detail about individual parameters beyond what the schema already provides. Baseline 3 is appropriate.

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's function: 'Create or delete a Foundry folder.' This is specific with a verb and resource, and it distinguishes from sibling tools which focus on entities, worlds, and search. No ambiguity.

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: after creating a folder, pass the returned uuid as the folder argument when creating entities. It also notes a key limitation about not being able to find existing folders without structure:read, which guides when to rely on freshly-created uuids. It doesn't explicitly name alternatives, but none exist among siblings.

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