apex_add_hero_banner

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

Annotations indicate this is a mutation (readOnlyHint=false) but the description adds no further behavioral context. It does not disclose whether multiple hero banners are allowed, whether it overwrites existing banners, or any permission/side-effect details, which is a notable gap for a write operation.

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 one concise sentence that efficiently conveys the core purpose with no wasted words. It is well-structured and immediately readable.

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?

With a rich schema and output schema present, the minimal description is adequate for basic invocation, but it lacks usage guidance and behavioral notes. Given the tool's 11 params and dense sibling list, additional context on limitations or prerequisites would improve completeness.

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?

The schema fully documents all 11 parameters (100% coverage) with descriptions and defaults, so the description is not required to add parameter details. It mentions 'title, subtitle, CTA button, gradient background' but these align with schema fields without adding extra semantics.

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 action 'Add' and the specific resource 'hero banner', listing key components (title, subtitle, CTA button, gradient background). This distinguishes it from sibling add-* tools like apex_add_region or apex_add_button.

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 on when to use this tool, prerequisites (e.g., page must exist), or alternatives. There is no mention of exclusions or comparison with sibling banner/components, leaving the agent to infer from the name.

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