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

With annotations indicating readOnlyHint=false, idempotentHint=false, and openWorldHint=true, the description adds valuable context: idempotency by name for create_collection, and the crucial note that changes are not live until framer_publish. It does not cover permissions or error behaviors, but adds substantial behavioral insight beyond annotations.

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 a single dense sentence listing actions and details, which may be hard to parse quickly. It front-loads the main purpose but could be improved with better formatting for readability. It is somewhat verbose but every part seems relevant.

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 tool's complexity (7 parameters, multiple actions, no output schema), the description covers the key operations, example JSON structures, and an important post-condition (publish required). It misses edge cases or error handling, but is largely complete for correct invocation.

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 coverage is 100%, so the schema documents all parameters. The description enriches parameter semantics by explaining how action-specific arguments like fields_json and items_json are structured with examples, and notes field NAMES as keys for upsert_items. This adds meaning beyond the schema's basic descriptions.

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 resource (Framer CMS on a connected project) and enumerates four actions with specific behaviors, making the tool's purpose clear. However, it does not explicitly differentiate itself from sibling Framer tools like framer_canvas or framer_design, though the focus on CMS operations is distinct.

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 actionable guidance, such as 'stand up a Blog collection before writing posts' and 'Changes are NOT live until framer_publish', which implicitly tells when to use this tool versus the publishing sibling. It lacks explicit 'when not to use' or alternative tools, but the context is sufficient.

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