taxme_snapshot

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

With no annotations, the description carries the burden of behavioral disclosure. It states the primary output (breadcrumb/url) and the optional screenshot behavior, but does not mention side effects, error cases, or what happens if no page is loaded. The behavior is largely read-only, but this is not explicitly confirmed.

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 a single sentence with a semicolon, conveying both the default behavior and the optional flag. Every word is purposeful with no redundancy or filler.

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 tool with only one optional parameter and no output schema, the description provides the essential information: what information is returned and how to request a screenshot. However, 'breadcrumb/url' and 'PNG path' are ambiguous (e.g., is it a local file path or a URL?), leaving minor gaps.

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 single boolean parameter 'screenshot' is described in the description ('set screenshot:true for a PNG path'), adding meaning beyond the bare schema. The schema covers the parameter type, but the description clarifies its functional effect, which is helpful given the low schema description coverage.

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 that the tool provides the current page's breadcrumb/url and optionally a PNG screenshot path. It effectively distinguishes itself from sibling tools by focusing on page-state retrieval, though it lacks an explicit verb like 'get' or 'return'.

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 is given on when to use this tool versus alternatives. It does not mention that taxme_status or other navigation tools might be more appropriate for certain scenarios, nor does it state any prerequisites or exclusions.

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