query

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

The description very briefly mentions running a query with optional inputs but does not disclose any behavioral traits such as side effects, permissions required, rate limits, or return format. With zero annotations, the description carries full burden and fails to provide meaningful transparency.

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 concise sentence that is front-loaded with the primary action. However, given the low schema coverage and many siblings, a slightly longer description with more detail would be warranted.

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 tool has only two parameters and no output schema, but the description is extremely minimal. It does not explain the query language, return value, or how to use inputs. Sibling tools add context but the description itself is incomplete for effective selection and 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?

The description adds no meaning beyond the schema for the 'datalog_query' parameter. For 'inputs', it only says 'optional inputs' without explaining what they are or how to format them. With 0% schema description coverage, the description should compensate but does not.

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 verb 'Run a Logseq Datalog query' and identifies the resource (Logseq Datalog query), making the tool's basic function apparent. However, it does not differentiate from the sibling tool 'datascript_query', which may have a similar purpose.

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 usage guidance is provided. The description does not indicate when to use this tool over alternatives like 'datascript_query' or any other query-related sibling. There are no when-not-to-use or prerequisite details.

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