issue-meta-esdt-collection

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions creating and sending a transaction, implying a write operation, but doesn't specify permissions needed, network effects, transaction costs, or what 'send it' entails (e.g., destination). The phrase 'All the properties will be set to true' is unclear about behavioral implications. This leaves significant gaps for a transaction-issuing tool.

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 brief (two sentences) but includes vague phrasing like 'All the properties will be set to true' that doesn't add clear value. It's front-loaded with the main purpose, but the second sentence is redundant and unclear, reducing efficiency. It could be more streamlined by removing ambiguous statements.

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 that creates and sends transactions (implied mutation) with no annotations and no output schema, the description is insufficient. It lacks details on behavioral aspects (e.g., side effects, error handling), doesn't explain the transaction outcome or return values, and provides minimal context beyond the basic action. Given the complexity and lack of structured data, more completeness is needed.

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 100%, so the schema already documents all three parameters (tokenName, tokenTicker, numDecimals) with basic descriptions. The description adds no additional meaning about parameters beyond implying they are used to issue the collection. No syntax, format, or constraints beyond the schema are provided, meeting the baseline for high schema coverage.

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's purpose: 'Create a transaction to issue a MetaESDT token collection (MESDT) and send it.' It specifies the action (create and send transaction) and resource (MetaESDT token collection). However, it doesn't explicitly differentiate from sibling tools like 'issue-nft-collection' or 'issue-semi-fungible-collection' beyond mentioning MetaESDT specifically.

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 alternatives. It doesn't mention when this tool is appropriate, prerequisites, or how it differs from similar tools like 'issue-nft-collection' or 'issue-semi-fungible-collection' in the sibling list. The statement 'All the properties will be set to true' is vague and doesn't clarify usage context.

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