arango_query_profile

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

No annotations provided, so description bears full burden. It states 'return plans/stats' but does not mention read-only nature, required permissions, or potential side effects. For a profiling tool, safety traits are essential but omitted.

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, concise but at the expense of missing critical details. It is appropriately sized for a simple tool but could include more information without becoming verbose.

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 no output schema, no annotations, and low schema coverage, the description is incomplete. It does not clarify return value structure, bind variable syntax, or how to use 'database' override. A profiling tool typically needs more 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 only 25% (only 'database' has a description). The description adds no detail on 'query', 'bind_vars', or 'max_plans'. The term 'plans' vaguely relates to 'max_plans' but does not explain meaning or default behavior.

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 clearly states the tool explains a query and returns plans/stats for profiling. However, it does not explicitly differentiate from sibling tool 'arango_explain_query', which may also explain queries. The phrase 'for profiling' hints at but does not guarantee distinction.

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?

No guidance on when to use this tool versus alternatives like 'arango_explain_query' or 'arango_query'. No prerequisites, when-not-to-use, or context provided.

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