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

Annotations already declare write semantics (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description usefully adds persistence scope ('Saved to this account') and the eligibility restriction (library layouts only). It does not disclose what happens on a name collision, overwrite behavior, or whether saving is idempotent, which is the main remaining gap for a mutating tool.

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?

Two dense sentences, front-loaded with the action and the payload, followed by the destination and the restriction. No filler or redundant restatement of the title.

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 save tool with annotations present and no output schema, the description covers what is saved, where it lives, and what cannot be saved. It leaves open name-collision/duplicate behavior and the meaning of the required projectId/pageName/index triple beyond what the schema states.

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 only 50%: name and index are documented in the schema, but pageName and projectId are bare strings with no explanation anywhere. The description never mentions any parameter, so it does not compensate for the coverage gap at all.

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?

States a specific verb (save) and resource (one section), and enumerates exactly what is captured: layout plus copy, pictures, videos and per-button/per-badge choices. It also distinguishes itself from neighbors by naming the consuming tool (uichemy_insert_saved_section), so an agent can tell it apart from add_section, duplicate_section or set_global_section.

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?

Gives the use case (reuse in any other project), the follow-up tool (uichemy_insert_saved_section), the inspection tool (uichemy_list_saved_sections), and an explicit when-not exclusion: 'an AI or code section cannot be saved.' That is a complete routing set for this operation.

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