Autoload Manage

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

With no annotations, the description carries the behavioral burden. It discloses that autoloads are globally accessible by name when singleton=True, that state persists to project.godot, that remove only unregisters without deleting the file, and that flat parameters are a compatibility alias. This is strong behavioral disclosure, though it omits details like error cases or validation 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?

The description is dense but every sentence earns its place: a definition of the resource, a concise op list with parameter semantics, side-effect notes, and the canonical invocation shape. It is front-loaded and well structured without fluff.

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 tool with this complexity, the description is complete. It explains the domain, all operations, parameters, persistence, and call shape. Since an output schema exists, omitting return-value details is acceptable, and the behavioral notes cover the key side effects an agent needs to know.

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 must fully explain parameters. It does: list() has no params, add(name, path, singleton=True) documents each argument and the default, and remove(name) takes one param. It also clarifies the canonical payload shape and the compatibility alias, going well beyond the generic 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 clearly states what the tool does: manage Godot autoloads (scripts or scenes loaded at project start). It names concrete operations (list/add/remove) and defines autoloads precisely, making it easily distinguishable from sibling tools like script_manage or project_manage.

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 context is clear: this tool is for autoload management, and the operation list implies when it should be used. However, it does not explicitly state when to prefer this tool over alternatives or mention any exclusions, leaving some routing decision to the agent.

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