system_manage

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

No annotations are provided, and the description does not disclose behavioral traits such as mutability, side effects, or permissions. The op enum hints at sub-operations, but the description adds no behavioral context beyond what the schema already provides.

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 very short (two sentences) but under-specified. It does not front-load important information and contains a redirect instead of substantive content. Could be more effective if it provided a concrete purpose.

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 no output schema and a nested params object, the description is incomplete. It does not explain what the tool returns, how to construct 'params', or the behavior of each op value. Relies entirely on sibling tool and schema.

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%, so the baseline is 3. The description does not add any meaning beyond the schema's descriptions of 'op' and 'params'. It fails to elaborate on parameter usage, constraints, or format.

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 'Godot system operations' is vague and does not specify what the tool actually does. It fails to distinguish this tool from siblings like 'core_manage' or 'scene_manage'. No verb or specific resource is indicated.

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 using godot_catalog to discover available operations, but provides no explicit guidance on when to use this tool versus alternatives. No context or exclusion criteria are given.

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