get_folders

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Get available folders' implies a read operation, but it doesn't specify permissions needed, whether it returns all folders or a subset, pagination behavior, or error conditions. The description lacks critical behavioral context for a tool with no annotation support.

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 extremely concise at three words, which is appropriately sized for a simple retrieval tool. It's front-loaded with the core action, though it could benefit from slightly more detail to improve clarity without sacrificing efficiency.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns folder data. It doesn't explain what 'available' means, what data is returned, or how results are structured. For a retrieval tool with zero structured support, the description should provide more context about behavior and outputs.

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%, with the single parameter 'space_duid' documented in the schema as 'Space DUID to get folders from'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for adequate but minimal value.

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 'Get available folders' states a clear verb ('Get') and resource ('folders'), but it's vague about scope and doesn't distinguish from potential siblings. It doesn't specify whether this retrieves all folders, user-accessible folders, or folders with specific characteristics, leaving the purpose somewhat ambiguous.

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 no guidance on when to use this tool versus alternatives. With siblings like 'create_folder' and 'get_dartboards', there's no indication of whether this is for listing folders versus creating them, or how it relates to other retrieval tools. No context about prerequisites or exclusions is mentioned.

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