add_home_section

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

Annotations only set destructiveHint: false, which the description does not expand upon. The description fails to disclose whether the tool is idempotent, what permissions are needed, or what happens on duplicate titles. No behavioral context beyond the bare minimum.

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, clear sentence that conveys the primary action and key parameters. No extraneous information is included.

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 incomplete. It does not mention the return value (e.g., ID of the created section), nor does it address optional parameters or system behavior (e.g., limits, conflicts).

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?

With 0% schema description coverage, the description partially compensates by naming the three required parameters (title, subtitle, description) but omits the optional ones (hidden, display_order). It does not explain data types, constraints, or the function of optional fields.

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 a story section to the home page') and specifies the key components (title, subtitle, description). It distinguishes from other add_* tools by targeting the home page resource, but does not elaborate on what constitutes a 'story 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?

No guidance is provided on when to use this tool versus alternatives like update_home_section or remove_home_section. There are no prerequisites, conditions, or exclusions mentioned.

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