Create a new agent by providing a name. Optionally specify an organization ID to assign the agent to a specific org.
Create a new agent.
| Name | Required | Description | Default |
|---|---|---|---|
| org_id | No | Org ID (uses active org if omitted) | |
| agent_name | Yes | Name for the agent |
Changes observed during successful MCP inspections.
v0.1.13Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Create a new agent,' omitting important traits like side effects, authorization needs, idempotency, or what happens on creation.
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?
Though composed of a single sentence, it is under-specified and fails to earn its place by providing insufficient information. True conciseness would pack more useful context into few words.
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 tool's 2 parameters, no output schema, no annotations, and many siblings, the description is severely incomplete. It does not explain return values, prerequisites, or how it differs from related tools.
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 baseline is 3 per guidelines. The description adds no additional meaning beyond the parameter descriptions in the schema.
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 states the verb 'Create' and the resource 'agent', making the purpose clear. However, it does not differentiate from many sibling create tools (e.g., forge_entity_create, forge_persona_create) beyond the name, leaving the agent unsure of what an 'agent' specifically is.
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 like forge_agent_update or other create tools. There is no mention of prerequisites, conditions, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.