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

Annotations already mark this as a non-read-only, open-world operation. The description adds meaningful behavior beyond that: it stores the key encrypted, validates the key against Bing, checks site verification, and warns against typing the key into a page. It does not detail failure modes, but it substantially explains what the tool does and why.

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 front-loaded and information-dense without being excessive. The sentence 'Free.' is abrupt, and the validation sentence is slightly compressed, but overall it earns its space.

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?

For a one-parameter connection tool with annotations and no output schema, the description covers the essentials: what is stored, that it is encrypted, that it is checked against Bing, and that the site must be verified. It could mention replacement/update behavior, but it is complete enough to call 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?

Schema coverage is 100%, so the schema already defines the single apiKey parameter. The description still adds value by saying where the key comes from (Bing Webmaster Tools, Settings, API access) and how it should be handled, going beyond the schema's terse 'The key, as Bing shows it.'

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?

It states a specific verb ('Store') and resource ('the founder's Bing Webmaster API key') and explains the downstream effect: letting Shipfound read Bing's page data and send pages via Bing's API. This clearly distinguishes setup/connection from the sibling submission tool bing_submit.

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 a setup step and gives handling guidance ('The founder gives the key; never type it into a page for them'), but it does not explicitly say when to use it versus alternatives like bing_submit or index_status. Usage is inferable but not directly stated.

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