Save my brand

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

Annotations only declare readOnlyHint=false, confirming a write. The description adds no behavioral context beyond the input sources: it doesn't say whether saving overwrites an existing brand, creates duplicates, requires prior setup, or what the effect on sibling brand data is.

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 padding. It is appropriately sized, though it is arguably a touch thin for a mutation tool rather than verbose.

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 a write operation with no output schema and only a readOnlyHint annotation, the description should at least state the effect of saving and how it relates to add_brand. It covers ingest sources but not outcome, so it is minimally adequate rather than complete.

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 tool declares zero properties, so the description's note that the brand can come from 'your website or a short description of what you sell' is effectively the only documentation of accepted free-form input (schema is additionalProperties:true). Baseline for 0 params is 4.

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?

Clear verb+resource: it persists 'your brand' from either a website or a short description of what you sell. However, it does not distinguish itself from the sibling add_brand or explain how a 'save' differs from an 'add', leaving an agent to guess between them.

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?

Usage is only implied: the mention of 'your website or a short description' hints at acceptable inputs, but there is no explicit when-to-use statement, no when-not-to-use, and no routing to add_brand, get_my_brand, or clear_my_brand.

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