add_site

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

No annotations provided, so description carries full burden. Only mentions raising BingWebmasterError, but lacks details on mutation effects, idempotency, authorization, or side effects. Inadequate for a write operation.

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?

Fairly concise but includes redundant 'Args:' section that duplicates schema information. Could be trimmed to a single sentence without losing content.

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?

Output schema exists but description does not mention return value. Missing details like idempotency, prerequisites (e.g., account verification), rate limits, and error handling beyond the generic exception.

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 description coverage is 0%. The description explains site_url but ignores the 'self' parameter entirely. Even the Args section only covers one of two parameters, leaving meaning of 'self' ambiguous.

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 'Add a new site to Bing Webmaster Tools' clearly specifies the verb (add), resource (site), and platform. It distinguishes itself from sibling tools like add_blocked_url or add_connected_page.

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?

No guidance on when to use this tool vs alternatives, no prerequisites, and no mention of preconditions like site ownership or verification. The only hint is an error condition, but no contextual help for choosing this over other tools.

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