read_gdextension

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool reads configuration, but does not describe potential side effects, permissions, return format, or error behavior. While the operation is clearly read-only, the description adds no behavioral context beyond the literal action.

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, 'Read .gdextension config.', with no filler or redundant content. It is front-loaded and perfectly sized for the tool's simple purpose.

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 tool lacks an output schema, so the description should explain what is returned or any relevant context. It does not specify the return value (e.g., the parsed config content), error cases, or default behavior details beyond what the schema already provides. Given the simplicity of the tool, this is a notable gap.

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 input schema covers 100% of parameters, with the 'path' parameter documented as 'Path to .gdextension file (default: auto-detect)'. The description adds no additional parameter semantics, but since the schema is complete, a baseline score of 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 clearly states the tool reads .gdextension config files, using a specific verb ('Read') and resource ('.gdextension config'), which distinguishes it from other read_* tools like read_project_config or read_resource. It is unambiguous and directly reflects the tool's function.

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 usage is implied: use when you need to read a .gdextension file. However, the description does not explicitly compare with alternatives or provide when/when-not guidance, relying on the tool name and file extension for context. No exclusions or prerequisites are mentioned.

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