godot_catalog

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

The description does not disclose behavioral traits beyond 'browse.' No annotations are provided, so the description carries full burden. It lacks information about read-only nature, side effects, permissions, or output format. For a read-like tool, minimal behavioral disclosure is acceptable, but it barely meets the threshold.

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 a single, front-loaded sentence (11 words) with no superfluous content. Every word earns its place, clearly conveying purpose and usage context.

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 simplicity (one optional parameter, no output schema), the description adequately covers its purpose and usage guidance. It does not elaborate on the 'operation tree' concept, but the context is sufficiently complete for an exploration tool.

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% (the single enum parameter is described in the schema as 'Optional domain to inspect'). The description adds no additional meaning beyond this. Baseline 3 is appropriate since the tool is simple and the parameter is already well-documented.

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 the tool's purpose: 'Browse the Godot MCP operation tree before choosing a domain tool.' It uses a specific verb ('Browse') and resource ('operation tree'), and distinguishes itself from sibling domain-specific tools (e.g., core_manage, scene_manage) by positioning itself as a preliminary exploration step.

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 explicitly advises using this tool 'before choosing a domain tool,' providing clear context for when to invoke it. It implicitly suggests that after browsing, one should select a specific sibling tool, though it does not explicitly describe when not to use it or list alternatives.

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