add_component

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

With no annotations, the description must carry the full behavioral burden. It only says 'Add a component' and gives parameter descriptions; it does not disclose that this is a mutating operation, whether duplicate components are allowed, whether the entity must exist, what happens on failure, or any side effects. This is a significant gap for a mutation tool.

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 short and front-loaded with the one-line purpose, followed by a compact Args list. All sentences contribute meaning, though the Args list partially mirrors schema fields; its added value justifies 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?

For a simple two-parameter tool, the description covers what the tool does and all arguments, but it omits behavioral context such as preconditions, error handling, and effect on existing components. With no annotations, this is a minimum-viable description rather than a fully complete one.

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 is the only source of parameter meaning. It clearly defines both required parameters: entity_id identifies the target entity, and component_type names the component with concrete examples such as 'Mesh' and 'PhysX Dynamic Rigid Body'. This fully compensates for the empty 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?

States a specific action ('Add'), a direct object ('a component'), and a target ('an entity'). The verb and resource make it distinct from sibling tools like remove_component or get_entity_components, so the agent knows what operation this performs.

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 this is the tool to use when you want to attach a component to an existing entity, but it does not explicitly state when to prefer it over alternatives, nor does it mention prerequisites like the entity existing or the component type being valid. No exclusions or edge-case guidance is provided.

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