axom_mcp_exec

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

The description adds significant behavioral context beyond annotations. Annotations indicate destructiveHint=true and readOnlyHint=false, but the description elaborates with security details (allowed directories, input size limits), chain-reaction functionality with variable substitution, and specific conditions for write/shell operations. This provides valuable operational context that annotations alone don't cover.

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 well-structured with clear sections (Operations, Chain Reactions, Example, Security) and front-loads the core purpose. Most sentences add value, though the example could be slightly more concise. Overall, it efficiently communicates complex functionality without unnecessary verbosity.

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?

For a tool with no output schema and complex functionality (multiple operations, chaining, security constraints), the description provides substantial context. It covers operation types, chaining mechanics, security restrictions, and usage conditions. The main gap is lack of information about return values or error handling, but given the annotations and detailed operational guidance, it's reasonably complete.

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?

With 100% schema description coverage, the baseline is 3. The description adds some value by explaining the 'chain' parameter's purpose and providing an example, and it clarifies that 'target' serves as either a file path or command depending on operation. However, it doesn't significantly enhance understanding of parameters beyond what the schema already documents.

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 clearly states the tool's purpose with specific verbs and resources: 'Execute file operations and shell commands with chain-reaction support.' It explicitly lists the three operation types (read, write, shell) and distinguishes this tool from its siblings by emphasizing its execution capabilities, unlike analyze, discover, memory, or transform 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?

The description provides clear context for when to use this tool: for file operations and shell commands with chain support. It mentions that write and shell operations are disabled when AXOM_READ_ONLY=true, offering some exclusion guidance. However, it doesn't explicitly compare to sibling tools or provide detailed alternatives for specific scenarios.

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