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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is partly covered. The description still adds real value beyond that: the admission chain required before calling, the fact that submissions are classed as actor claims rather than established fact, and that a primary actor block is returned.

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?

Very short and free of filler, but the bracketed prerequisite is placed ahead of the purpose statement rather than after it, and the opening clause duplicates the tool title, making the front-loading slightly awkward.

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 non-read-only submission tool with no output schema and five parameters, the description covers the prerequisite and hints at the return shape, which is the minimum an agent needs. It omits failure behavior, whether submitted items can be amended or withdrawn, and any distinction from submit_result.

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 100%, so all five parameters including the actor_token credential and matter_id admission semantics are already documented in the schema. The description adds no syntax or format detail about any parameter, so the baseline 3 applies.

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 verb and resource ('Submit evidence') but 'evidence' is abstract, and the sentence largely restates the title. It adds that submissions are classified as actor claims and that the primary actor block is returned, which helps, but it never distinguishes this tool from the sibling atlas.submit_result, which an agent would plausibly confuse it with.

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 bracketed prerequisite '[NEEDS ADMISSION: enroll, then atlas.bind_actor]' gives a clear ordering constraint for use. However, there is no guidance on when to choose this over alternatives such as atlas.submit_result or atlas.raise_challenge, so routing is implied rather than explained.

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