core_manage

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

With no annotations present, the description bears full responsibility for behavioral disclosure. It omits any mention of side effects (e.g., whether operations are read-only or destructive), authentication needs, rate limits, or error behaviors. The schema's enum hints at possible actions, but the description itself adds no transparency.

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 extremely concise with two sentences, but the first sentence is overly generic and lacks substance. While brevity is positive, the content is insufficiently informative, making it less effective. The structure is simple but the trade-off between brevity and clarity is not well-balanced.

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 complexity (2 parameters, enum of 7 operations, nested 'params' object) and the absence of an output schema, the description is severely lacking. It does not explain return values, error handling, or the structure of the 'params' object for each operation. Compared to the rich sibling tool set, this description leaves the agent underinformed.

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 both parameters are described in the schema: 'op' as an enum and 'params' as an object. The description adds no further meaning beyond the schema, which already defines the parameter purposes. A baseline score of 3 is appropriate since the schema carries the load without description enhancement.

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 core operations' is vague and does not specifically define what 'core' means in this context. It hints at functionality through the enum in the schema but lacks a clear verb-resource statement. The reference to godot_catalog adds some direction but does not clarify the tool's unique purpose among many sibling manage tools.

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 only guidance is 'Call godot_catalog for the operation tree,' which suggests where to find possible operations but does not explain when to use this tool versus alternatives like system_manage or runtime_manage. No conditions, prerequisites, or exclusions are provided, leaving the agent uncertain about tool selection.

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