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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the tool's safety profile is covered. The description adds that it returns raw TOON text, which is useful, but doesn't disclose pagination behavior or potential large response sizes. No contradiction.

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 concise and front-loaded with the core purpose. It uses a compact format to explain parameters, but the sentence about refs is somewhat cryptic and could be clearer. Still, it's efficient with no 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 tool has only 3 optional parameters and no output schema, so the description is somewhat adequate. However, with no output schema, it should describe the return value format more thoroughly (e.g., structure of the TOON text), which it only mentions as 'raw TOON text'. Additionally, the page parameter is left undefined. Given the tool's moderate complexity, it's incomplete but not severely lacking.

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 0%, so the description must compensate for parameter meaning. It explains the effect of each parameter (onlyProjects, parentReference) decently, but page parameter is not mentioned at all. This is a significant gap since the description doesn't explain pagination.

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 lists folders/projects with specific filtering options, distinguishing it from other folder-related tools like magnific_folders_get, create, delete, rename. It also mentions the output format (raw TOON text), which adds specificity.

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: no params for top level, onlyProjects for projects, parentReference for children. It also notes that refs work with creations/folder tools, hinting at integration with other tools. However, it doesn't explicitly state when not to use it or compare with sibling folder tools.

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