query_rules

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

With no annotations, the description bears full responsibility for disclosing behavior. It only states the query parameters, omitting whether the operation is read-only, what results are returned, or any side effects. The agent cannot infer safety or scope.

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 extremely concise (one sentence) but at the cost of omitting crucial information. While there is no redundancy, the brevity leads to under-specification, making it less helpful than a longer, more detailed 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?

Given the tool's complexity (7 parameters, no output schema, no schema descriptions), the description is severely incomplete. It does not cover return values, error conditions, or the behavior of optional parameters, leaving the agent with insufficient 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?

The description mentions only 2 of 7 parameters ('language', 'filePath'), leaving 'tags', 'maxRules', 'matchMode', 'projectId', and 'fileContent' completely unexplained. Schema description coverage is 0%, so the description must compensate but fails to add any semantic value for the majority of 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 specifies the verb 'query' and resource 'rules' along with key parameters 'language' and 'filePath', making the basic purpose clear. However, it does not differentiate from the sibling 'list_rules' and does not clarify what 'query' entails (e.g., filtering vs. retrieving).

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 is provided on when to use this tool versus alternatives like 'list_rules' or 'cognition_query'. There are no hints about prerequisites, use cases, or exclusions.

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