watchSchematicFromNetlistFile

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

No annotations are provided, so the description bears the full burden. It discloses the polling and regeneration behavior and mentions update events, but omits important details like blocking behavior, side effects on existing schematics, and requirements. It is adequate but not fully transparent.

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 two sentences, front-loaded with the core action, and contains no redundant information. Every word earns its place.

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?

With 12 parameters, no schema descriptions, no annotations, and a polling tool that may have stateful behavior, the description is far from complete. It omits parameter explanations, prerequisites, error handling, and return format details beyond 'update events'. The output schema may help but is not referenced.

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 schema description coverage is 0%, meaning no parameter descriptions in the schema. The tool description does not explain any of the 12 parameters, leaving the agent to guess their meaning or rely on naming conventions. This severely hampers correct invocation.

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 action ('poll a netlist file and regenerate schematic') and the resource ('netlist file' and 'schematic'). It distinguishes itself from siblings like syncSchematicFromNetlistFile by emphasizing polling and continuous monitoring.

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 usage for watching a netlist file over time, but it does not explicitly state when to use this tool vs alternatives like one-time sync tools or when not to use it. The guidance is implied but not explicit.

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