query_economic_graph

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

With no annotations, the description bears full burden for behavioral disclosure. It only states 'query the graph' without revealing any traits (e.g., read-only, rate limits, pagination, or what the output represents). The existence of an output schema helps but the description adds no behavioral context.

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, which is concise but severely underspecified. The brevity comes at the cost of completeness; it does not earn its place because it provides almost no actionable information beyond the tool name.

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 moderate complexity (2 parameters, many siblings, and an output schema), the description is extremely inadequate. It fails to explain what the knowledge graph contains, how to craft queries, or what the response looks like, leaving the agent with minimal guidance 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 0%, meaning no parameter descriptions exist, and the tool description adds no meaning to the two parameters. It does not explain what format the 'query' string should take or what 'max_depth' controls, leaving the agent without essential usage details.

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 states the action 'query' and the resource 'curated macroeconomic knowledge graph', which is clear in a general sense. However, it does not specify the scope of queries or differentiate from sibling tools like search_series or get_series_metadata, making it somewhat vague.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of what types of queries are appropriate or when the tool should be avoided.

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