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

With no annotations provided, the description carries the full behavioral burden. It discloses the refundable stake, escrow parking, 10% slashing on overturned disputes, and even contrasts it with a spent provider listing fee. These are critical consequences an agent must know before making a real call.

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 lengthier than a one-liner but every sentence earns its place. The invite flow, body summary, refund/slashing behavior, and auth are all packed with signal. It is not overly verbose, though a small amount of tightening around the 'website bounce' sentence would be possible.

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?

This is a well-covered tool: invite-only, stakeholder economics, exact parameter constraints, and auth requirements are all present. It does not explicitly state the successful response format, but the agent has the endpoint and the request shape, and the schema is present. The only minor gap is that the description's 'list of 1 to 7' for specializations does not note the schema's null/optional default.

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%, and the description fully compensates by explaining all three fields: wallet_id as a UUID you own, specializations as a constrained 1-7 element list of exact allowed values, and stake_amount as an integer 10000. It also adds out-of-band rules (422 on invalid values), which the schema alone does not provide.

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 opens with a specific verb and resource: 'Register as a RAREEAI oracle by staking joules (POST /oracle/register).' This directly states the tool's function and distinguishes it from siblings like oracle_deregister and oracle_assess. The endpoint further reinforces a clear, unambiguous purpose.

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 clearly says this is INVITE-ONLY at launch, describes the behavior for non-whitelisted wallets, and states the required auth ('verified account + marketplace:write'). It implicitly tells the agent when registration will succeed and what happens otherwise. It does not explicitly name the alternative deregistration tool, but the gate and context are strong enough.

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