issue-semi-fungible-collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool creates and sends a transaction, implying a write operation, but lacks details on permissions, costs, network effects, or what 'All the properties will be set to true' entails. This leaves significant gaps in understanding the tool's behavior and risks.

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 concise with two sentences that directly address the tool's function. However, the second sentence ('All the properties will be set to true') is vague and adds minimal value, slightly reducing efficiency. Overall, it's well-structured and front-loaded with the main action.

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?

Given the complexity of issuing a token collection (a write operation with potential side effects), no annotations, and no output schema, the description is incomplete. It fails to explain return values, error conditions, or the implications of 'All the properties will be set to true', leaving the agent with insufficient context for safe and effective use.

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 has 100% description coverage, with clear documentation for both parameters ('tokenName' and 'tokenTicker'). The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline of 3 for adequate but not enhanced parameter semantics.

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 action ('Create a transaction to issue a semi-fungible collection (SFT) and send it') and specifies the resource ('collection'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'issue-fungible-token' or 'issue-nft-collection', which would require mentioning unique aspects of semi-fungible tokens to earn a 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 alternatives like 'issue-fungible-token' or 'issue-nft-collection', nor does it mention prerequisites or exclusions. It only states what the tool does, leaving the agent to infer usage from context without explicit direction.

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