Run an Asterisk CLI command

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

The annotations declare readOnlyHint=true, but the description states that setting PBX_MCP_ALLOW_WRITE=true lifts the read-only restriction, implying the tool can perform write operations. This directly contradicts the read-only annotation, so the contradiction rule applies.

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 two sentences and around 50 words, front-loading the tool's purpose and output format. Every sentence adds essential information: what it does, the default restriction, and how to change it.

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 single-parameter CLI runner with no output schema, the description covers purpose, output, command restrictions, and configuration. It could mention the risk of enabling write mode, but overall it is sufficiently complete for this simple tool.

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?

The schema description for 'command' already includes concrete examples (pjsip show endpoints, queue show support) and covers 100% of parameters. The tool description adds valuable semantic constraints by specifying that only inspection commands are allowed by default, which helps the agent select valid commands.

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 uses a specific verb ('Run') and resource ('Asterisk CLI'), and clearly states that it returns raw output. It distinguishes itself from sibling tools by being the generic CLI runner for Asterisk, as opposed to the more specific status/channel/endpoint wrappers.

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: it is for inspection commands in the default read-only mode and only lists permitted command categories like 'core show', 'pjsip show', and 'queue show'. It also explains how to lift the restriction via PBX_MCP_ALLOW_WRITE=true, though it does not explicitly mention when to prefer sibling tools.

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