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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=true), and the description adds genuinely non-derivable behavior: operations are records/requests rather than automatic canon changes, missing authorization or evidence yields a rejection, and world_id is reused across later operations. It stops short of describing receipt/response behavior, but the additions are substantive.

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?

Five tight sentences, front-loaded with the operation summary before the propose requirements. Dense and mostly waste-free, though the middle sentences pack several distinct rules that could be marginally sharper.

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 14-parameter, no-output-schema tool, the description covers operation semantics, propose prerequisites, cross-operation identity reuse, and failure semantics (rejection vs approval). What is missing is any sense of what a successful submission returns, which the absence of an output schema leaves slightly open.

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 coverage is 100%, so baseline is 3. The description goes beyond the schema by tying parameters into a workflow: propose requires evidence, counterevidence, falsifier, and at least two distinct dimension_changes, and the returned world_id feeds subsequent operations. That cross-parameter guidance is real added value.

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?

States a specific verb (submit) and resource (world proposal, challenge, evaluation, audience projection, publication request) and locates it 'through the existing review gate.' It explicitly distinguishes itself from explore_cassie_world, which is the read path for the same resource.

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?

Names the alternative for reading ('Use explore_cassie_world to read worlds') and gives a conditional prerequisite for propose. It does not explain when to choose challenge vs evaluate vs project_audience vs submit_publication, so the routing among its own operations is left to the enum and schema.

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