remove_home_section

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

The description states it removes a section, which is destructive, and annotations already provide destructiveHint: true. However, the description does not add further behavioral context (e.g., permanence, cascading effects, permission requirements).

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 very concise (one short sentence), which is good for efficiency. However, it misses useful details, making it under-specified for a tool that likely needs context about the parameter.

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?

Given the tool's complexity (one required parameter, no output schema), the description should clarify the source of the ID and any side effects. It does not, leaving the agent with insufficient context to use the tool correctly.

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 coverage is 0%, and the description does not explain the 'homepage_entity_id' parameter. The agent is not told what this ID represents or how to obtain it, leaving the parameter undocumented.

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 'Remove a story section from the home page' clearly states the action (remove) and the resource (home page story section). It distinguishes from sibling tools like 'add_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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing to list home sections first to obtain the ID, or any conditions under which removal is appropriate.

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