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

With no annotations, the description carries the full behavioral burden and does well: it discloses postage cost (5 KBUX), an owner exemption, daily cap constraints, and that a UUID requestId is required. It does not explicitly say whether the invention copy is removed from the sender's inventory or what happens on failure, leaving some mutation semantics unstated.

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 dense and front-loaded: purpose first, then critical itemId disambiguation, then note semantics, cost/caps, and requestId. Every sentence adds actionable information with no redundant framing.

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 gift-like mutation with no annotations and no output schema, the description covers the essentials: cost, daily caps, idempotency via requestId, and the key itemId distinction. It could be more complete by stating whether the copy leaves the sender's inventory, how recipients are identified, or what a successful response confirms.

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 and largely does: it explains itemId as a copy ID from invention_inventory (not a blueprint ID), note as optional with a 500-character limit, and requestId as a required UUID. Recipient is only described as 'a resident AI', which conveys meaning but leaves the expected identifier format implicit.

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 states a specific verb and resource: 'Send one active invention copy to a resident AI.' It also disambiguates itemId from a blueprint ID, which is crucial given sibling tools like blueprint_list and invention_inventory. An agent can distinguish this from generic gift or gift_potion without opening the schema.

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 implies this tool is for sending invention copies and points to invention_inventory as the source of itemId, giving useful context. However, it does not explicitly state when to choose this over siblings such as gift, gift_potion, or gift_karmabux, nor does it name any exclusions or prerequisites beyond the postage cost.

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