get_tools

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

No annotations provided, and description only states a read-like operation ('list'), but does not disclose any side effects, authentication needs, rate limits, or response structure. Agent cannot infer behaviors like idempotency or safety beyond the surface.

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 short sentences, front-loaded with core purpose, zero redundant words. Every word adds value.

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?

No output schema, no annotations, and minimal description leaves significant gaps: no return format, no pagination info, no distinction from sibling tools beyond name. Agent lacks essential context for correct invocation.

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% for the single parameter 'chains', but description adds value by clarifying it's optional and specifying comma-separated format, which is not explicit in schema description.

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?

Description uses specific verb 'List' and resource 'available tools' with concrete examples (bridges, DEXes), clearly distinguishing it from siblings like get_chains (list chains) or get_quote (get quotes).

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?

Implies use when listing tools is needed, but lacks explicit when-not, prerequisites, or comparisons with alternatives. The optional chains filter is mentioned, but no guidance on when filtering is necessary.

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