godot_get_dependencies

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

Annotations declare readOnlyHint=true and destructiveHint=false, which already tells the agent this is a safe query operation. The description adds minimal behavioral context beyond that—it doesn't disclose what a dependency graph looks like, whether transitive dependencies are returned, or any performance implications. With annotations covering the safety profile, a 3 is appropriate.

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?

A single sentence that states the verb, the resource queried (dependency list), and the input type. Zero wasted words.

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 output schema exists and the description names its purpose, but there's no mention of whether dependencies include only external resources or also internal references, or whether the list is recursive. The description is adequate but leaves ambiguity for deeper queries.

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 path parameter has a fully descriptive schema definition that includes resource and scene path examples. With schema_description_coverage at 100% for this single parameter, the description adds nothing beyond what the schema already documents. Baseline 3 is appropriate.

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 states a specific verb (Query) and resource (dependency list for a scene/resource/script). It communicates the core purpose clearly)Skip. However, it doesn't explicitly distinguish itself from siblings like godot_list_project_files or godot_audit_orphans, so it's not fully differentiated.

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?

No guidance on when to use this tool versus alternatives, no mention of supported input types, output format, or typical use cases. The agent must infer when dependency queries are appropriate.

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