Read scraper

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

Annotations already indicate readOnlyHint=true, so the description's disclosure of returning source and metadata adds modest value. It does not, however, describe error behavior (e.g., if the scraper doesn't exist) or any side effects. Given the tool's simplicity and the annotation coverage, the description meets the minimum bar but does not exceed it.

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, concise sentence that front-loads the verb and resource. Every word is necessary; there is no redundancy or irrelevant information. It is perfectly sized for a simple retrieval tool.

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 tool's low complexity (one required parameter, existing output schema, and annotations providing safety profile), the description is complete. It states what the tool returns (source and metadata), and the output schema covers the return structure. No additional information is needed.

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 100% (the only parameter 'name' has a description). The tool description adds no additional meaning about the parameter beyond what the schema already provides. Therefore, it meets the baseline of 3.

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 uses a specific verb 'Return' and identifies the resource as 'a saved scraper's source and metadata.' This clearly distinguishes it from siblings like 'scraper_list' (lists scrapers) and 'scraper_run' (executes a scraper), making the purpose unambiguous.

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 explicit guidance on when to use this tool versus alternatives. While it's implied that you would use this to retrieve a specific scraper's details, there is no mention of when to avoid it (e.g., if you only need the name, use scraper_list) or prerequisites. The context is clear enough for a simple tool, but the lack of explicit guidance leaves room for error.

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