assert_title

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

With no annotations, the description carries full burden but only states the basic assertion logic. It does not disclose whether it waits for the title to match, whether it throws an exception on failure, or if it is a soft or hard assertion. This is insufficient for an agent to understand the tool's behavior.

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 sentence with 8 words, very concise. However, it sacrifices essential detail; a slightly longer description would improve clarity without becoming 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 the absence of annotations, output schema, and parameter descriptions, the description is too minimal. It does not explain error handling, return values, or behavioral specifics like timeouts. The tool's complexity (2 parameters, assertion logic) demands more than a single sentence.

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 mentions 'expected text' and implies a mode via 'exact', but does not explain the meaning of the 'exact' parameter (e.g., that false means contains). The default value is not clarified, and there is no additional semantic detail beyond what the parameter names hint.

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 clearly states the tool's purpose: asserting that the page title equals or contains expected text. The verb 'assert' combined with 'page title' and the two modes (equals or contains) make it distinct from sibling assertion 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?

No guidance is provided on when to use this tool versus other assertion tools (e.g., assert_url, assert_text) or when to choose exact vs. contains mode. The description lacks context about prerequisites or alternatives.

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