godot_get_class_info

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

The description mentions specific data categories (inheritance, properties, methods, signals) but does not describe return format or any potential side effects. The annotations already indicate read-only and idempotent behavior, so the description adds only moderate detail beyond annotations.

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, concise sentence that directly states the tool's function without unnecessary words or repetition. It is easy to parse and quickly understood.

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?

The description is sufficient for a simple query tool, but it does not provide context about when to invoke it, what the output looks like, or how it relates to other query tools. Since an output schema is present, the description need not explain return values, but it lacks usage context that would make it fully self-contained.

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?

The description does not mention any parameters, and schema description coverage is 0% (the tool description does not reference the params). While the schema itself has descriptions for each field, the description fails to compensate for this lack of coverage, leaving parameter semantics entirely dependent on the 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 the tool's purpose: to query class inheritance, properties, methods, and signals from ClassDB. It specifies a concrete action (query) and target (ClassDB), making it distinct from the many sibling tools that perform mutations or other queries.

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 provides no guidance on when to use this tool versus alternatives, such as godot_get_node or godot_get_version. It lacks context about typical use cases or situations where this query is the appropriate choice.

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