arthas_ognl

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

No annotations are provided, so the description must disclose behavior. It only says 'execute', implying state mutation but not stating side effects, safety, or required permissions. The agent is left uninformed about whether OGNL expressions can modify the application or if they are read-only.

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 extremely concise, one sentence of four words. While compact, it lacks structure and front-loading of key information. For a tool with three parameters, more context would improve usability without sacrificing brevity.

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?

Given no annotations, no output schema, and three parameters, the description is incomplete. It does not explain what OGNL is, what the output looks like, or important constraints like timeout behavior. The tool executes user-defined expressions, which could be risky; this is not mentioned.

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%, so the schema already documents the three parameters. The description adds no additional meaning beyond the schema's parameter descriptions. Baseline score of 3 is appropriate as no extra value is provided.

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 'Execute OGNL expressions' states the verb and resource but is vague. It does not differentiate from sibling tools like arthas_exec or arthas_getstatic, which also execute code or access values. The term 'OGNL' is not explained, leaving ambiguity about what expressions are supported.

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 is given on when to use this tool versus alternatives. With many sibling Arthas tools for executing code, inspecting state, or monitoring, the description provides no context for selection, such as prerequisites or typical scenarios.

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