Analyze application logs

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

No annotations are provided, so the description carries the full burden, and it does disclose meaningful traits: the logs are live-tail (not archived, implying ephemeral/non-historical data) and the response is an analysis-ready aggregate rather than raw entries. It still omits the read-only safety profile, permission requirements, and any latency or streaming caveats around live-tail fetching.

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?

Two sentences with zero filler; the capability and payload shape come first, then the routing preference. Nothing is repeated from the schema and every clause earns its place.

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?

With no output schema, the description usefully characterizes the return payload, and the rich parameter schema covers input details. It is nearly complete for a read tool of this complexity, though pagination/offset behavior on a live-tail stream and failure modes when no target is reachable are left unstated.

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 description coverage is 100% across 16 parameters, including defaults, ranges and enum values, so the schema already documents parameter meaning thoroughly. The description adds only indirect context (the priority/logger/instance fields that searchTerms match against), so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Fetch live-tail logs for a Mule application') and goes further by naming the shape of the returned payload (normalized lines plus counts by priority, logger and instance). It explicitly distinguishes itself from the sibling anypoint_list_app_logs, so an agent can route without opening either schema.

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 gives a clear selection rule: 'Prefer this over anypoint_list_app_logs when diagnosing a problem.' It names the alternative and the condition that favors this tool. It stops short of stating when the sibling is the better choice (e.g., raw paginated log listing), so it is not fully bidirectional guidance.

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