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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the operation is a public read GET, implying safety, and enumerates endpoints. However, it does not disclose potential errors, rate limits, or response variability, which would be valuable for a generic endpoint fetcher.

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 sentence that front-loads the main purpose, then provides a comprehensive list of endpoints. While long, every endpoint listed is a useful example, and there is no redundant wording.

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 is a simple generic GET fetcher, and the description covers the host, scope, and a broad list of valid paths. There is no output schema, so some return format context could be helpful, but given the variety of endpoints, endpoint-specific responses make that impractical.

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 for the single parameter 'path' is 100%, so the baseline is 3. The description adds concrete examples of valid paths including placeholders like <pool> and <sig>, which enriches the parameter semantics beyond the schema's generic 'Endpoint path including query string.'

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 performs GET requests to public read endpoints on rpc.aex402.com, with a specific verb and resource. It distinguishes itself from specialized siblings like aex402_getPool by covering all other endpoints, though it doesn't explicitly contrast with them.

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 any public read endpoint on the host, listing many examples. It doesn't explicitly state when to use this instead of specialized aex402_* tools, but the broad scope and endpoint list make the intended context reasonably clear.

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