Update website settings

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

The description indicates a mutation ('update') which is consistent with the idempotentHint annotation. It does not provide additional behavioral details such as side effects, permissions, or the idempotent nature beyond what the annotation already conveys.

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 sentence, front-loaded with the action, and contains no redundancy. It efficiently conveys the tool's purpose.

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 complexity (15 parameters, nested objects, no output schema), the description lacks detail on default behavior, parameter structure, and return values. It is minimally complete for a simple understanding but insufficient for confident usage.

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 description gives a high-level overview of what parameters relate to (content, contact, SEO) but does not map to specific parameter names. With 0% schema coverage, it fails to compensate adequately for the 15 optional parameters.

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 resource ('global content, official company link, contact details and SEO displayed dynamically on the public frontend'). It distinguishes from sibling tools which deal with categories, services, posts, etc.

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 implies this is for global site settings but does not explicitly state when to use it versus alternatives like save_category or save_service. No when-not or exclusion criteria provided.

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