gluedly_get_snapshot

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

With no annotations provided, the description carries the full burden of explaining behavioral traits. 'Fetch' implies read-only behavior, but the description does not explicitly state that this does not trigger a new scrape or that snapshot_id defaults to the latest snapshot when omitted.

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?

A single sentence with no filler, front-loading the key action and the two useful return modes. It is compact but still informative enough to be scannable.

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?

The parameter schema handles the input requirements well, and the description identifies the main output forms, but no output schema and no annotations leave the tool lifecycle unclear. The description could better say whether the snapshot must already exist and how this tool relates to trigger_scrape.

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 coverage is 100%, so the parameters page_id, format, and snapshot_id already have clear descriptions. The description adds a small semantic layer by explaining the return options, but it does not significantly go beyond what the schema already provides.

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 names the action ('Fetch'), the resource ('a page snapshot'), and the two output forms ('clean extracted rows' or 'prompt-ready Markdown'). This clearly distinguishes the tool from the sibling tools: it is about retrieving snapshot data, not listing pages or triggering a new scrape.

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 intended usage is implied: call this tool when you want the extracted content from an existing page snapshot. However, the description does not explicitly say to use gluedly_trigger_scrape when a fresh snapshot is needed, nor does it mention the lifecycle between creating and fetching a snapshot.

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