oraclaw-mcp-server

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

Includes useful latency information (<1ms) not found in schema, but lacks critical behavioral details like statefulness, side effects, or return value structure given no annotations exist.

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 compact and front-loaded with key technical terms, though the density sacrifices explanatory depth that could help tool selection.

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?

Fails to compensate for missing output schema by describing return values, and omits differentiation from other optimize_* siblings in the toolkit.

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% description coverage, meeting the baseline; description mentions algorithm names but adds no semantic context beyond the schema's own definitions.

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 identifies the bandit algorithms used and the explore/exploit purpose, though it doesn't explicitly differentiate from sibling tools like optimize_cmaes or optimize_contextual.

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 prefer this over alternative optimization strategies (e.g., CMA-ES for continuous spaces) or when the bandit approach is inappropriate.

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