Organize compendium

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

Beyond the annotations, the description discloses meaningful behavioral details: the folder is created if needed, entries are matched exactly by name ignoring case or by id, and unmatched or ambiguous names are reported and left in place. It also points to lock behavior via the export-to-compendium reference, giving the agent useful execution expectations.

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?

Three short sentences front-load the core action and then add only essential behavioral details. No filler or repetition exists; every sentence contributes useful 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?

The description covers purpose, matching rules, failure behavior, folder creation, and lock rules, which is substantial for a mutating tool. It does not describe the return value or fully explain the unlockIfNeeded parameter, but the absence of an output schema and the presence of behavioral details keep this from being a major gap.

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?

The description adds real meaning to the entryNames parameter by explaining exact-case-insensitive matching and ambiguous-name handling, and clarifies folderName by noting the folder is created if needed. However, the optional unlockIfNeeded parameter is left unexplained, and the lock-rule reference is indirect.

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: sorting/moving compendium entries into a folder, with the folder created if needed. It is specific about the resource and behavior, but it does not explicitly differentiate this tool from related compendium operations like import-from-compendium or delete-compendium-entries.

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?

No explicit guidance is given about when to use this tool versus alternatives. The description mentions 'Same lock rules as export-to-compendium,' which references another tool, but does not explain when organizing is appropriate or when a different compendium operation should be chosen.

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