assert_title

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

With no annotations, the description carries the full behavioral disclosure burden. It does convey that this is an assertion operation supporting exact and substring matching, but it does not disclose what happens on failure, whether the title is fetched fresh, or whether the tool is non-mutating.

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, front-loaded sentence with no filler. Every word contributes to understanding the tool's purpose and primary behavior.

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 simple two-parameter assertion tool, the description provides a minimally viable understanding. However, without annotations or an output schema, it should ideally also explain the exact flag semantics and failure behavior to be fully 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?

Schema description coverage is 0%, so the description must compensate. It identifies the 'expected' parameter as the text to match and hints at the 'exact' parameter through 'equals or contains', but it does not explicitly state that exact=true means exact match and exact=false/default means contains.

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 names a specific verb ('Assert'), a specific resource ('page title'), and the core behavior ('equals or contains expected text'). This clearly distinguishes it from sibling tools like assert_url or assert_text.

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 the tool is used when verifying the page title against expected text. However, it does not explicitly state when not to use it or point to alternatives such as assert_url or assert_text, leaving the usage guidance implicit.

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