runPrologQuery

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the core action and prerequisite (loaded definitions) but does not disclose whether the query can have side effects, what the return format is, or how errors are handled. For a query execution tool, this is a significant transparency gap.

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, efficient sentence with no filler words. It immediately states the action and prerequisite, earning a top score for conciseness.

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?

With no output schema and no annotations, the description should explain what the tool returns or behaves. It only says 'executes a query' without specifying results, side effects, or error conditions. For a simple tool this might seem adequate, but the lack of any behavioral or return information makes it incomplete for an agent trying to invoke it correctly.

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 description coverage is 100% for the single 'query' parameter, which already explains it as 'The Prolog query to execute.' The tool description adds no additional parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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 action: 'Executes a Trealla Prolog query against loaded definitions.' It uses a specific verb ('executes') and resource ('Prolog query against loaded definitions'), which distinguishes it from sibling tools like loadProgram, saveSession, and loadSession, which deal with loading/saving rather than executing 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?

The description implies when to use this tool: after definitions have been loaded. 'Against loaded definitions' gives clear context that the query depends on a prior loadProgram call. However, it does not explicitly mention when not to use it or discuss alternatives, so it falls short of a 5.

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