query_aave_subgraph

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

No annotations are provided, so the description must fully disclose behavior. It describes the action as executing a raw GraphQL query, which implies read-only, but does not explicitly state it is non-destructive or mention any side effects, rate limits, or authentication needs.

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 concise yet packed with information: purpose, usage condition, prerequisite, and entity lists. Front-loaded with the key usage rule, every sentence earns its place.

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?

For a raw query tool, it provides entity lists and chain options, but lacks explanation of output format or error handling. However, given standard GraphQL responses and the complexity of the tool, it covers essential usage context well.

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% with descriptions. The description adds value by enumerating chain options (from the enum) and suggesting use of get_aave_schema for query construction, aiding parameter comprehension beyond 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?

The description clearly states the tool's purpose: execute raw GraphQL queries when pre-built tools are insufficient. It specifies the verb 'execute' and resource 'AAVE chain's subgraph', and distinguishes from sibling tools by indicating it's a fallback option.

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?

Explicitly says 'Use this when a pre-built tool doesn't cover the user's need' and advises to 'Use get_aave_schema first to explore available entities and fields'. Lists entities for lending and governance schemas, providing clear context for use.

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