create_agent

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

With no annotations, the description bears the full burden. It discloses the layout behavior and role restrictions, but does not detail side effects, idempotency, or error conditions. For a creation tool, this is adequate but not comprehensive.

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 front-loaded with purpose and includes an Args section, but the layout details (40:60 split, pane numbers) are verbose and may not be necessary for tool invocation. It could be more concise.

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 the presence of an output schema, the description covers purpose, parameters, and return values. However, it lacks context on prerequisites (e.g., whether a workspace must exist) and potential errors. It is 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 coverage is 0%, so the description must add meaning. It provides descriptions for all parameters and indicates allowed values for 'role' and 'ai_cli'. However, it contradicts the schema by marking 'caller_agent_id' as required ('必須') while the schema lists it as optional. This inconsistency reduces reliability.

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 clearly states '新しいエージェントを作成する' (create a new agent) and provides specific layout details, making the purpose clear. However, it does not explicitly distinguish from sibling tools like 'initialize_agent', though the layout details imply a specific type of agent creation.

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 implies usage for creating a new agent with specific roles, and notes 'Owner と Admin のみ使用可能' (only Owner and Admin can use). However, it does not provide guidance on when not to use or mention alternatives like 'initialize_agent'.

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