oraclaw-mcp-server

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

Discloses performance characteristic ('Sub-millisecond') but fails to specify return format/structure since no output schema exists.

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?

Extremely tight at 9 words with zero redundancy; every token provides specific functional, algorithmic, or performance information.

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 simple 3-parameter tool but misses critical return value documentation required by absence of 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 has 100% coverage, establishing baseline; description reinforces 'method' parameter options by naming algorithms but adds no semantic value for 'threshold' or 'data'.

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 anomaly/outlier detection function and specifies algorithms (Z-score/IQR), distinguishing it from sibling analysis/optimization 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 no guidance on when to use Z-score vs IQR methods or when to choose this over other analysis tools like analyze_graph.

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