aras_run_query

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

It discloses that it does not actually run the query, a key behavioral trait not covered by annotations, and explains that it returns the structure instead, providing transparency about its capabilities and limitations.

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?

Concise two-sentence structure, front-loaded with the primary purpose, and includes necessary limitation context without extraneous detail.

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 description gives a high-level idea of the return (query structure and tool suggestions) but lacks specifics on the format or content of the returned structure, leaving some ambiguity since no output schema is provided.

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?

The description does not elaborate on the meaning or usage of parameters like 'nome', 'maxRighe', or 'parametri'. Given the minimal schema, this lack of explanation leaves ambiguity about how to specify the query name or parameters.

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 that the tool attempts to execute a saved query but, due to a known limitation, returns the query structure and suggests alternative tools. This distinguishes it from siblings like aras_query_items that actually perform queries.

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?

It explicitly mentions that execution is not possible from an external client and directs users to alternative tools for data retrieval, making it clear when to use this tool (to get the structure) and when to use others.

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