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

With no annotations provided, the description carries the full behavioral burden. It does disclose the returned content (design notes and complete HTML) and the page/all-pages scope, but it omits operational traits such as read-only nature, permissions, response size, or pagination, leaving meaningful gaps.

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 short and front-loads the main output (design notes and complete HTML) before adding scope and mode details. The second sentence is an imperative rather than invocation guidance, but it is concise and does not bloat the definition.

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 4-parameter retrieval tool with no annotations, no output schema, and low schema coverage, the description is too thin. It does not explain the required template id, the effect of mode, the meaning of noodle, or how multiple pages are returned, leaving an agent with important unanswered questions.

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 25%, and the description does little to compensate. It mentions page selection and all-pages behavior, which duplicates the schema's page description, but it does not explain the required 'id' parameter or clarify what 'noodle' and 'mode' enum values mean beyond being selectable variants.

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 states a specific retrieval: a template's design notes and the complete HTML of one page or all pages. It is clear enough to distinguish from tools like list_templates or get_component, but it does not explain the domain-specific 'noodle' and 'mode' terms or differentiate itself from siblings such as get_design_guide or get_noodle.

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?

There is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives among the many sibling tools. The closing instruction 'Save each page as .html' implies a post-retrieval action but does not help an agent decide when this tool is the right choice.

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