vechainstats_get_contract_code

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the action ('get') and resource, giving no details about return format, error handling, or behavior when the contract is not verified. This lack of behavioral transparency is a significant gap.

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 succinct sentence that is front-loaded with the verb. It is appropriately sized for the tool's apparent simplicity, containing no unnecessary words or repetition.

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 has no output schema and no annotations, so the description must provide complete context. It does not explain the return value format, how 'expanded' modifies results, or any failure scenarios. Given the undocumented parameter and missing behavioral details, the description is inadequate for an agent to fully understand the tool's usage.

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 describes only the 'address' parameter (50% coverage), leaving 'expanded' undocumented. The description adds no information about either parameter, failing to clarify the purpose or effect of the boolean 'expanded' flag. With schema coverage not high, the description should have compensated but does not.

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 'Get verified contract source code' uses a clear verb ('Get') and a specific resource ('verified contract source code'), distinguishing it from sibling tools like vechainstats_get_contract_info which likely returns metadata. However, it does not explicitly contrast with alternatives or mention the Vechain network, so it falls short of a perfect 5.

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 alternative tools. It does not mention prerequisites (e.g., contract must be verified), alternatives, or exclusions. Users are left to infer usage solely from the tool name and description, which is insufficient.

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