add_deep_link_block

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

The description only mentions that the tool adds a block and raises BingWebmasterError on failure. It does not disclose behavioral traits such as whether it is destructive, mutative, or requires specific permissions. Without annotations, the description fails to provide sufficient behavioral context.

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 very concise with only a few lines, but it is under-specified. It lists arguments and errors in a structured docstring format, which is easy to parse, but the brevity comes at the cost of completeness.

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 of the tool (5 required parameters, no annotations, no output schema details), the description is insufficient. It does not explain what a deep link block is, what the return value looks like, or how to use the tool correctly in context. The presence of an output schema is not utilized in the description.

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 has 0% description coverage, and the description only lists parameter names without explaining their meaning or constraints. For instance, 'self' is not defined, and the other parameters have inferred but not explicit semantics. The description adds minimal value beyond the schema itself.

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 states the action 'Add a deep link block' which is a specific verb+resource. It clearly indicates what the tool does, though it lacks explanation of what a deep link block is. The name and description are sufficient to distinguish from sibling tools like add_blocked_url or add_connected_page, but the resource's purpose is not elaborated.

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 is provided about when to use this tool versus alternatives like add_blocked_url or add_page_preview_block. There is no information about prerequisites, context, or situations where this tool should or should not be used.

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