list_agent_commands

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

No annotations provided. Description mentions server parameter default, but lacks details on pagination, ordering, read-only nature, or output specifics. Some behavioral info, but insufficient to fully inform an AI agent.

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, front-loaded with purpose. No fluff, but could be slightly more structured. Efficient for its length.

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?

Output schema exists, so return values are covered. However, with 5 parameters and only one explained, the description leaves gaps. Adequate but not comprehensive.

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%, meaning no parameter descriptions in schema. Description only adds meaning for 'server' (target server default). No explanation for page, size, search, sort_by. Minimal compensation for low coverage.

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?

Description clearly states the tool lists the history of remote commands sent to agents, including status and output, distinguishing it from siblings like run_agent_command (send commands) and list_agents_with_commands (list agents with commands).

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 explicit when-to-use or alternatives. Usage is implied by the description, but no guidance on when not to use or compared to similar tools.

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