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

readOnlyHint=true is consistent with "opens nothing by itself," and the description adds value beyond the annotation by stating the return shape (screens, buttons, fields) and the required follow-up tool family. It stays silent on how the tool knows which asset and collection to target given zero parameters, which is the one behavioral question an agent will have.

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 core behavior is front-loaded, but the second sentence is a crowded run-on with a parenthetical, and the closing fragment "Brandfolder's official API: Yes." is dangling and ambiguous about what it is asserting.

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 zero-parameter, no-output-schema tool the description does cover what comes back and what to do next, which is the main burden. It leaves unresolved how the target asset and collection are identified and what the cryptic official-API note means, so it is adequate rather than complete.

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?

With zero parameters there is no schema semantics to extend, so the baseline applies. The description does not explain that the asset/collection context must come from the preceding conversation, which is the implicit "input" for a parameterless guidance tool.

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?

Names a specific verb and resource (add asset to collection) and then discloses the actual artifact: it returns step-by-step Brandfolder instructions rather than performing the action. The opening sentence reads as if the tool itself adds the asset, so the clarification arrives one sentence late, but the combination is unambiguous enough to distinguish it from the cotlet_browser_* execution tools.

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?

"opens nothing by itself; then do it with the cotlet_browser_* tools" gives an explicit handoff sequence, which is exactly the guidance an agent needs for a planner/browser split. It does not say when NOT to use it (e.g. when a direct write tool would suffice), so it stops short of a 5.

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