monitor

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

With no annotations, the description carries the full burden and largely succeeds. It discloses persistence behavior (snapshots stored under PYRECRAWL_MONITOR_DIR), the exact status vocabulary (new/unchanged/changed/error), and the unified-diff output on change. A minor gap is that 'forget' is not described as destructive/deleting snapshots, and 'history' output details are missing.

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 compact and front-loaded with a one-sentence purpose statement followed by a tight parameter list and key behavioral facts. There is no filler; each sentence contributes operational value.

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 four-parameter tool with an output schema, this is close to complete. It covers what the tool does, how snapshots persist, what actions exist, and what a check returns. The only meaningful omissions are precise behavior of 'history' and 'forget,' and possible error conditions, but these are not critical for correct invocation.

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 explain the parameters, and it does. url is self-evident, action lists its enum values, prefer is cross-referenced to scrape, and css_selector gets a practical purpose. The 'prefer' explanation is terse but useful given the sibling tool. This goes well beyond the bare 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?

The opening line 'Track a URL over time and report meaningful content changes' states a specific verb, resource, and temporal scope. It clearly distinguishes monitor from siblings like scrape (single fetch) and crawl (site traversal) by emphasizing change tracking over time. The action list (check/history/forget) further clarifies the tool's role.

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 provides clear context: this is for monitoring a URL over time and detecting changes. It explains when each action is appropriate (check for current diff, history for past snapshots, forget to stop monitoring), and even gives guidance on using css_selector to avoid false positives. It does not explicitly name alternatives or state 'use this instead of scrape,' but the purpose is unambiguous enough.

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