add_home_section

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

Annotations only declare destructiveHint=false. The description adds that this is a creation operation and names the content fields, but it does not disclose how optional fields like hidden or display_order behave, where the section is inserted, or whether it appends to the page. No contradiction with 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 front-loaded sentence with no filler. Every word contributes to identifying the action, target, and core content of the operation.

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 creation tool with five parameters and no output schema, the description is underspecified. It covers the required fields but gives no guidance on optional behavior, ordering, visibility, or return value, making it minimally viable but incomplete.

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 0%, so the description must compensate. It names title, subtitle, and description, which correspond to the three required properties, but it entirely omits hidden and display_order, leaving two of the five parameters semantically unexplained.

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 verb ('Add') and resource ('story section to the home page') and lists the core content fields ('title + subtitle + description block'). It clearly distinguishes itself from siblings like update_home_section, remove_home_section, and list_home_sections.

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 gives clear context: this tool creates a new section on the home page. Sibling names imply that update_home_section is for modifying an existing section and remove_home_section for deleting one, but the description does not explicitly state these alternatives or exclusions.

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