td_monitor_visual

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

Annotations indicate a non-readonly mutation (readOnlyHint=false, openWorldHint=true). The description adds context that default mode omits base64 frames to reduce tokens, which aligns with schema parameters (include_image, confirm_high_token_mode). No contradiction; some side effects hinted but not fully detailed.

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?

Two sentences, front-loaded with the core purpose. No wasted words; efficient and easy to parse.

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 output schema, description covers key behavior (periodic monitoring, token management). Missing explicit link to td_stop_monitor_visual, but for its complexity it is adequate.

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 covers 100% of parameters, so baseline is 3. The description adds value by explaining the default behavior regarding base64 frames, which relates to the include_image parameter, going beyond the schema.

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?

Description clearly states 'Start periodic monitor for a TOP', identifying the action (start) and the resource (periodic monitor on a TOP). This distinguishes it from sibling tools like td_stop_monitor_visual and td_capture_and_analyze.

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 periodic monitoring but does not explicitly contrast with alternatives like single capture (td_capture_and_analyze) or streaming (td_stream_top). The note about default token usage is helpful but not a full guideline.

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