Call a raw Blockscout API endpoint

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 response is capped in size and the endpoint path is relative to /api/v2. It does not discuss error handling or mutation, but for an escape hatch this is acceptable.

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 two sentences with no unnecessary words. The first sentence defines purpose, the second provides parameter guidance and response constraint. Highly efficient.

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 complexity of an escape hatch tool with 4 parameters and an output schema, the description is complete. It explains the tool's purpose, input format, pagination via cursor, and response size cap. The output schema covers return values.

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 schema already documents all parameters. The description adds minimal parameter-specific information beyond what is in the schema, such as emphasizing that endpoint_path is relative to /api/v2 with an example. Baseline is 3 due to high schema 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 the tool is an escape hatch for calling any Blockscout REST v2 endpoint not covered by a dedicated tool, with a specific verb 'call' and resource 'any Blockscout REST v2 endpoint'. This distinguishes it from sibling tools which handle specific endpoints.

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 this tool should be used when no dedicated tool exists ('not covered by a dedicated tool'). It provides an example endpoint path and mentions response size cap, but does not explicitly list when not to use it or alternative tools.

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