create_header

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Create' and gives no information about side effects, defaults, relationship to the current selection, or what happens when optional parameters are omitted. This is a significant gap for a mutation 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?

The description is a single, front-loaded sentence with no filler. It quickly conveys the primary purpose. It could add more value without becoming bloated, but as written it is appropriately concise.

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 tool with 6 optional parameters, no output schema, and no annotations, the description is under-specified. It does not explain what the tool returns, how parentId determines placement, what the default behavior is with no parameters, or whether the created header/hero is a grouped structure.

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 100%, and the description mentions three of the six parameters (heading, subheading, CTA) but adds no meaning beyond the schema. It provides no context for width, parentId, or brandColor, so it neither compensates for gaps nor enriches the existing schema 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 uses a specific verb ('Create') and names the resource ('page header/hero') with the key content pieces (heading, subheading, CTA). It is clear what the tool produces, though it does not explicitly distinguish itself from sibling creation tools like create_frame or create_nav_bar.

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?

No guidance is provided about when to choose this tool versus alternatives such as create_section, create_nav_bar, or create_frame. The description does not mention selection prerequisites, parent requirements, or when a header/hero is the appropriate construct.

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