read_raw_collection

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

No annotations are provided, so the description carries the burden of disclosing behavior. It indicates a read operation and mentions filtering/pagination, but it does not explicitly state that it is read-only, potential side effects (though unlikely), or any auth/rate limit considerations. It adds context about the raw scraped data, but could be more explicit.

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 action ('Read documents'), specifies the resource ('CHRawdata database'), and mentions key features. Every word earns its place with no redundancy.

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 tool has a full schema and an output schema, so the description does not need to explain return values. It covers purpose and basic behavior effectively. However, it lacks explicit usage guidelines compared to alternatives, so it is not fully complete for guiding an agent on when to use it.

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 schema has 100% coverage with detailed descriptions for all parameters. The description mentions 'filtering and pagination' which loosely maps to filter_query, skip, limit, and sort_by, but it adds no additional detail beyond what the schema already provides. Baseline 3 is appropriate.

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 the tool reads documents from the CHRawdata database (raw scraped data) with filtering and pagination. It distinguishes itself from the sibling 'read_collection' by specifying the specific database, 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?

The description implies usage for raw scraped data but does not explicitly state when to use this tool over alternatives like 'read_collection'. There is no mention of when not to use it or exclusions, leaving the guidance somewhat implicit.

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