wpf_watch_property

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

No annotations exist, so the description must fully disclose behavior. It only says 'Monitor a property for changes' without stating if it blocks, returns immediately, is continuous, or has side effects. This is insufficient for an agent to predict tool impact.

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?

Extremely concise at 4 words, but at the expense of critical information. Conciseness should not sacrifice completeness; this is under-specification, not efficient brevity.

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 no output schema, no annotations, and only two bare parameters, the description is severely incomplete. A tool that monitors properties requires details on return format, duration, error handling, and interaction with the UI thread—none provided.

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?

With 0% schema coverage, the description should add meaning to parameters. Neither 'property_name' nor 'element_handle' are explained beyond their names. No hints on format, constraints, or relationship between parameters.

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 uses verb 'Monitor' and resource 'property', indicating a watching function. However, 'monitor' is vague—does it set up a subscription, poll, or return on change? It distinguishes from siblings like 'wpf_get_element_properties' (snapshot) and 'wpf_set_property' (mutation), but the lack of specificity reduces clarity.

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 like 'wpf_get_element_properties' for one-time retrieval or 'wpf_get_bindings' for binding info. The description does not explain context, prerequisites, or when not to use.

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