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

Annotations already declare write (readOnlyHint=false), non-destructive, idempotent, and open-world behavior. The description adds real value beyond that: a validation gate that refuses bad URLs before any network fetch, and a deterministic output path that explains why the operation is idempotent. It does not explicitly say whether an existing imported/ARTIFACT_ID.html is overwritten, which keeps it from a 5.

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?

Two sentences, no filler, with the core action and destination path front-loaded and the validation constraint immediately after. Every clause earns its place.

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 simple two-parameter tool with full schema coverage, annotations, and no output schema, the description covers the action, destination, and input validation adequately. The only missing piece an agent might want is what happens when the target file already exists, though idempotentHint implies overwrite-or-noop semantics.

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 both parameters are already documented (id = Project UUID, url = artifact URL pattern). The description restates the URL pattern and adds the rejection behavior for malformed URLs, but adds nothing about the id parameter beyond the schema. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 (import), a specific resource (a published Misar artifact page), and the exact destination path (imported/ARTIFACT_ID.html). No sibling tool performs this operation, so the agent can distinguish it immediately from the surrounding project/file tools.

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 establishes a hard precondition — the URL must match the exact misar.ai/code/artifact/ARTIFACT_ID pattern — which tells the agent when this tool will work and when it will be rejected before any fetch. It does not name alternatives or explicitly say when not to use it, but no sibling tool overlaps with this operation.

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