update_home_section

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is partly covered. 'All fields must be supplied' usefully implies full-replacement semantics (existing values are overwritten rather than merged), which goes slightly beyond the annotations, but the description says nothing about permissions, what a partial call does, or side effects on ordering/visibility.

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?

A single front-loaded sentence with no filler, and the update target is stated first. It is terse to the point of under-specification, but as a sizing/structure matter it is clean.

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?

This is a destructive, fully-required mutation on six parameters with only 17% schema coverage and no output schema, so the description carries a lot of burden and discharges almost none of it. It omits what gets overwritten, where the section ID comes from, and any prerequisite listing step.

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 17% (only homepage_entity_id is documented), so six required parameters rely almost entirely on bare type declarations for title, subtitle, description, display_order, and hidden. The description's 'all fields must be supplied' merely restates the schema's required array and adds no meaning about the fields' content, formats, or constraints.

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?

States a specific verb (update) and resource (home page story section), which clearly separates it from list_home_sections, add_home_section, and remove_home_section. It does not name any sibling or explain how the update differs from add, but the purpose itself is unambiguous.

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 only guidance is the schema-level constraint that all fields must be supplied; there is no statement of when to choose update_home_section versus add_home_section or remove_home_section, and no prerequisites such as where the section ID comes from. An agent must infer the usage context entirely.

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