query

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that the tool is read-only (non-destructive), whether it affects data, or any rate limits. The description is silent on these aspects, leaving the agent without critical safety information.

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?

Two sentences plus a reference link. Front-loaded with action and scope. No redundant words. The link provides additional detail without bloating the description.

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?

Missing key details: the output format of results is not mentioned, which is crucial for a query tool. The 'limit' parameter is not explained in the description. The tool has no output schema, so the description should compensate. The link helps but does not cover what the agent needs to know immediately.

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%, so baseline is 3. The description adds value by mentioning supported query types (property, tag, task), which helps construct the 'query' string beyond the schema description. This context is meaningful for correct usage. However, it does not elaborate on 'limit' or 'result_type' beyond 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?

Clearly states it executes a Logseq DSL query to search pages and blocks, specifying supported query types (property, tag, task, logical). Effectively distinguishes from sibling tools like 'search' which likely does free-text search, and 'find_pages_by_property' which is simpler.

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?

Provides context on supported query types, implying use for complex structured queries. However, it does not explicitly mention when to use this tool over siblings (e.g., 'search' or 'find_pages_by_property'), nor does it state when not to use it. The link to documentation partly compensates but does not provide direct guidance.

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