Recommend rerank strategy

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

Description states 'feeds the RAG Reranker Pipeline category in audit_database,' which suggests a write operation, contradicting the readOnlyHint=true annotation. No disclosure of side effects or safety. The 'feeds' wording is ambiguous and potentially misleading.

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, concise and front-loaded with key purpose. However, the mention of 'four analytics' is inconsistent with the five listed components, reducing clarity.

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?

Does not list the four analytics, mentions five components instead. Lacks guidance on when to use this tool vs. individual analyzers. Does not explain the output schema or how results are consumed. Incomplete for a roll-up advisor with 3 parameters and output schema.

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 only 33% (database param described). The description mentions 'days' but does not explain its meaning or default behavior. retrieval_index is not explained at all. The description fails to compensate for low schema coverage.

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 is a roll-up advisor over four analytics for one window, returns a summary and list of findings. Names specific components (reranker_idle, topk_stable, etc.). Distinguishes from sibling analytics tools by explicitly acting as a consolidator.

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?

Implied usage as a roll-up over analytics, but no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives (e.g., using individual analyzers) or exclusions.

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