add_autoload

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

With no annotations, the description discloses behavioral traits: singleton defaults true, path auto-prefixing, and a crucial warning about headless mode crashing. Lacks detail on return values or side effects beyond the warning.

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 well-structured sentences: main action first, then critical warnings and alternative usage. No wasted 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?

Missing output schema explanation; does not describe what the tool returns on success. While it covers errors and warnings, the lack of return info leaves a gap for completeness.

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 100%, raising baseline to 3. Description adds value by explaining autoloadPath accepts 'res://...' or relative paths and that singleton defaults true, which goes beyond schema property 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?

The description clearly states 'Register a new autoload in a project' with specific verb and resource. It distinguishes from sibling tools like update_autoload by noting that errors occur if name exists and suggesting update_autoload as alternative.

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?

Explicitly tells when to use (register new autoload) and when not to (if name exists, use update_autoload). Also provides context on no Godot process required and warns about headless mode, aiding appropriate usage.

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