find_n_plus_one

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

Lacks annotations, so description must cover behavioral traits. Only states it fingerprints and flags patterns, but no details on what flags look like, side effects, rate limits, or scope of 'recent query history'. Insufficient for an agent to anticipate behavior.

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, front-loaded with primary action. Efficient but could benefit from slight expansion on usage context 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 no parameters, the description should provide more context about return value, how to interpret results, and how it fits with siblings. Currently incomplete for an agent to use confidently.

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?

No parameters exist; baseline is 4. The description adds no parameter info, which is acceptable since there are none. Schema coverage is 100% due to empty 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?

The description clearly states the tool detects N+1 query patterns from recent query history, using fingerprinting and flagging. It is a specific verb-resource pair that distinguishes from sibling tools like 'explain_query' or 'optimize_query'.

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 vs alternatives. Does not mention prerequisites, intended workflow, or when to avoid. The '[ARCHITECT tier]' tag hints at audience but not usage context.

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