Godot API reference

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

No annotations are provided, so the description carries the burden. It communicates that results reflect the exact installed engine version and that queries are read-only ('Look up'). It does not disclose pagination/truncation behavior, but the verb and scope make side-effect-free lookup clear.

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?

Two sentences, front-loaded with the core action, and supported by a crisp list of return contents. The second sentence is a direct, no-waste usage tip.

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?

With 6 parameters and no output schema, the description covers the core lookup semantics and result contents, while schema fills in param constraints. It doesn't mention response formatting or pagination, but the default limit and offset are in the schema, so the information is recoverable.

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 already covers query, kind, project, and inherited well; the description adds meaning by tying returned categories to the kind selector but leaves limit/offset unexplained. With 4 of 6 params having schema descriptions, the description is adequate but not highly additive beyond 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 verb 'Look up' plus resource 'Godot class in the installed engine' is specific, and the list of contents (methods, properties, signals, enums, inheritance) distinguishes it from generic search or list tools. It also brands itself as an authoritative API reference with exact engine version, which differentiates it from sibling 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 line 'Use this instead of recalling the API' gives a clear trigger condition for reliance on this tool, while 'installed engine' scopes it to version-accurate lookups. It doesn't explicitly contrast sibling tools, but the intended use case is evident.

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