xae_list_commands

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds the introspection intent but says nothing about result volume, truncation, or how the limit interacts with a large command set — relevant context that annotations do not supply.

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?

A single front-loaded sentence with the filter scope stated before the parenthetical rationale. Nothing is wasted, though it is arguably too terse given the undocumented defaults.

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?

An output schema exists, so return-value documentation is not required. However, for a tool with two unannotated parameters and surprising defaults (contains='PLC', limit=200), the description leaves the agent guessing about default filtering and result capping.

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 0%, so the description must carry both parameters. It conceptually explains 'contains', but ignores 'limit' entirely and never warns that 'contains' silently defaults to 'PLC', a non-obvious default that will filter results unexpectedly.

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 ('List DTE command names') plus the filtering dimension ('containing a substring'), which is enough to distinguish it from a generic command executor. It gestures at the sibling relationship by framing this as discovering 'what this shell exposes', but never names xae_command as the tool that actually runs a command.

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 parenthetical 'to discover what this shell exposes' implies the intended discovery/introspection use case. There is no explicit when-not guidance and no named alternative, so the agent must infer that this is the read-only precursor to xae_command.

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