update_aeo

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only says 'Update' without mentioning side effects, whether existing markup is replaced or merged, or any potential destructive outcomes. This is insufficient for a mutation tool.

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 words. It efficiently conveys the core purpose and the plan requirement, earning every word.

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 has no annotations, no output schema, and an empty input schema, the description must compensate by explaining parameters, behavior, and effects. It fails to do so, leaving the agent unprepared for a tool that likely requires specific inputs and has side effects.

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 input schema is empty with additionalProperties:true, so there are no formal parameters documented. The description does not explain what keys or values the tool expects, such as how to specify FAQPage, HowTo, or speakable markup content. This leaves the agent without guidance on how to construct a valid call.

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 (update) and the resources (FAQPage, HowTo, speakable markup). However, it does not explicitly differentiate from sibling tools like update_seo or update_geo, though the specific markup types make it reasonably distinct.

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 includes a prerequisite (PRO plan or higher), which is a form of usage constraint, and implies it is for structured data markup updates. However, it provides no explicit guidance on when to use this tool versus alternatives, leaving the agent to infer from the name and sibling list.

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