mystorax_axiom_tool_call

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

No annotations are provided, so the description carries full behavioral disclosure burden. It does disclose the fail-closed token requirement (a genuinely useful security behavior), but doesn't describe side effects, whether calls are read-only or mutating, rate limits, or error behavior when not allowlisted. Sparse behavioral context for a proxy/invocation tool.

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?

The description is a single dense sentence that conveys purpose and a critical security invariant (fail-closed without token) efficiently. No wasted words, though the sentence is packed and slightly opaque on first read.

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?

This is a proxying tool with 3 parameters including nested arguments object, 0% schema coverage, no output schema, no annotations, and several sibling tools to disambiguate against. The single-sentence description is insufficient to guide correct invocation; it needs parameter semantics, usage disambiguation from siblings, and expected return/behavior context.

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 coverage is 0% so the description must compensate, but it only partially does. The description implies 'tool' names the Axiom tool and 'arguments' are its params, but provides no detail on the 'tool' naming format, what 'arguments' expects, or the meaning of timeout_s (units, defaults, behavior on timeout). Since 0 params are described, the description carries responsibility it doesn't fully meet.

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 states it 'Call[s] one allowlisted Axiom tool via Conductor' which gives a clear verb+resource. However, it doesn't distinguish from sibling mystorax_axiom_tool_search, and the 'Axiom tool' concept is left unexplained, so an agent can't tell what 'allowlisted' means or what this actually accomplishes versus the search sibling.

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 provided on when to use this tool versus alternatives like mystorax_axiom_tool_search or the routing guide. The description mentions fail-closed behavior but doesn't tell the agent how to choose between this and sibling tools, nor what prerequisites or context are needed before invoking.

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