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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The '1 credit' disclosure is genuinely useful cost/pricing context beyond the annotations. No mention of rate limits or result shape, so not a 5.

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?

Two dense sentences, front-loaded with what the tool returns, followed by the cost. Nothing wasted.

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?

Covers purpose and cost, but for a search tool with pagination (page max 10) and optional locale params, the description doesn't clarify pagination behavior or proxy-based country routing. No output schema exists, so the description could say more about result format. Adequate but with clear 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?

Schema coverage is 75%, with q, country, and language described in the schema; page has no schema description. The description adds no parameter details, but with high coverage the baseline of 3 is appropriate. The agent learns nothing from the description it cannot get from the 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?

States a specific verb (search) and resource (academic papers) plus the added value (citations and PDF links), which distinguishes it from the generic 'search' and other vertical siblings. It doesn't explicitly name a sibling it is NOT, so it stops short of 5.

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 mention of citations and PDF links implies academic use, but there is no explicit when-to-use guidance vs the sibling 'search' or 'patents', and no exclusions or prerequisites. Usage is only inferable.

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