send_command

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

No annotations provided. Description mentions 'allow_dangerous: allow dangerous commands explicitly' which hints at safety behavior, but contradicts schema regarding caller_agent_id requirement. Lacks details on authentication, side effects, or response behavior.

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?

Well-structured: one-line summary, usage note, Args section, Returns. Efficient but a bit verbose due to Japanese. Each part 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?

Complex tool with 4 params, no annotations, 0% schema coverage. Description lacks full explanation of return format, missing output schema details, and has a contradiction about required parameter. Incomplete for reliable use.

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?

With 0% schema coverage, description provides brief explanations for each parameter (target agent, command, dangerous flag, caller agent). Adds some value but is minimal and in Japanese. Does not fully compensate for lack of schema descriptions.

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 'Send a command to a specified agent.' The verb 'send' and resource 'agent' are specific. However, it does not distinguish from sibling 'broadcast_command' which sends to all agents, missing differentiation.

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?

Provides access control info: 'Only Owner and Admin can use.' This is a usage guideline but does not specify when to use this tool vs alternatives like broadcast_command.

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