Genomic-Agent-Discovery

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

With no annotations, description carries full burden. It discloses the polling pattern and return filtering ('addressed to you or broadcast'), compensating partially for missing output schema. However, it omits whether messages are consumed/destructively removed or persistent, and lacks safety/permission context.

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, zero waste. First sentence states purpose; second combines usage frequency with return value description. Efficiently front-loaded with no redundant phrases.

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?

Adequate for a zero-parameter read operation. Description compensates for missing output schema by documenting return content (filtered messages). Lacks annotations but covers essential behavioral context for coordination use case.

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?

Zero parameters present, establishing baseline 4 per rubric. Description appropriately focuses on behavior rather than parameters, requiring no additional parameter semantics.

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?

Description uses specific verb 'Check' with resource 'agent chatroom for messages'. Clearly distinguishes from sibling 'send_message' (outbound vs inbound) and all genetic/medical query tools.

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 explicit polling frequency guidance ('Call every 5-10 tool uses') and explains coordination purpose. Lacks explicit 'when not to use' or alternative comparison, but the frequency directive strongly guides invocation timing.

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