wpf_assert

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

With no annotations, the description carries the full burden and does well: it discloses that mismatch throws, that passing assertions are persisted while recording, and that ambiguous or absent IDs fail before any input is used. It stops short of describing what a successful call returns or whether other state changes occur.

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?

Dense and front-loaded with the core behavior first, then alternatives, then targeting rules. The semicolon-chained clauses make a few statements terse to the point of being cryptic (e.g. 'missing or duplicate IDs fail before input').

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 five-parameter assertion tool with no output schema and no annotations, the description covers targeting, comparison semantics, failure behavior, and recording side effects. The main gap is the return value/result shape on success, which nothing else supplies.

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, and it does: mutual exclusivity of element_handle vs automation_id, case-sensitive exact AutomationId matching, root_handle as a scoping modifier, and the '{null}' sentinel for expected_value. This adds substantial meaning beyond the bare schema types.

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?

States a specific verb and resource: asserts an element's dependency-property value via exact ordinal comparison of the invariant string. It also distinguishes itself from siblings by naming wpf_wait_for_element as the tool for asynchronous changes, so an agent can separate it from discovery/wait tools.

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?

Gives explicit preconditions and alternatives: 'Use wpf_wait_for_element first for asynchronous changes', and 'Target by exactly one of element_handle or automation_id'. The root_handle scoping rule and the fail-fast behavior for missing/duplicate IDs further constrain correct invocation.

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