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

No annotations are provided, so the description carries the full burden. It discloses that the server verifies on-chain payment and returns job_id, but it does not mention error handling, idempotency, or security implications. The transparency is adequate but minimal.

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 4 sentences with no fluff. It is front-loaded with the action ('Submit'), then prerequisites, then server action, then return value and next step. Every sentence adds value.

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 6 parameters (2 required) and an output schema. The description covers the main flow and return value (job_id) but misses details on optional parameters and error behavior. It is adequately complete for a sequential workflow step but lacks depth.

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%, meaning no parameter descriptions in the schema. The description only indirectly explains tx_hash and work_hash (from prerequisite context). It does not explain metadata, agent_sig, agent_pubkey, or artifact_uri, leaving the agent with incomplete guidance for all 6 parameters.

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 verb 'Submit', the resource 'work artifact', and the context 'on-chain notarisation (NEAR_DIRECT payment path)'. It also distinguishes from sibling tools by placing it as step 3 in the flow: quote -> pay -> notarize -> verify.

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 explicit prerequisites (sending NEAR and providing tx_hash) and tells the agent to use notary_verify for polling. It implicitly explains when to use this tool (after payment, before verification) but does not explicitly state when not to use it.

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