verify_api

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

With no annotations provided, the description must carry the full behavioral disclosure. It gives no information about side effects, read-only nature, return values, error behavior, or any operational traits. The word 'checks' implies a non-mutating query, but this is not explicitly stated. There is no contradiction, but the omission is total, leaving the agent completely uninformed.

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 short (one sentence), so it is not verbose, but this is under-specification rather than concise efficiency. It lacks essential structure and front-loading of key details. Every sentence must earn its place, but here there is only a vague phrase that provides almost no value.

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?

For a tool with two parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what results the agent should expect, how to interpret the check, or what actions might follow. The tool is part of a large sibling set, and without context it cannot be used correctly. Even a minimal operational note would improve this.

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 description coverage is 0%, so the description must compensate by explaining the parameters. It does not. The schema only names class_name and method_name, and the description adds nothing about what these mean, their formats, or relationships. The agent cannot infer valid values or usage from the description alone.

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 'Checks Godot API' states a verb ('checks') and a broad resource ('Godot API'), but it is too vague to convey a specific action. It does not say what aspect of the API is checked (e.g., class existence, method signature, compatibility). It fails to differentiate from siblings like validate_scene or validate_script, which also imply checking. This is borderline tautological and offers little actionable meaning.

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?

There is no guidance on when to use this tool versus alternatives. No mention of scenarios where verify_api is preferred over get_help or validate_script. The description gives no context about prerequisites, limitations, or exclusions. An agent would have no basis for choosing this tool over others.

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