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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, and the description still adds a real behavioral trait: file and image sources return an image only when a viewable copy or an original upload under 5 MB exists. It does not disclose that long content is truncated with a cursor, though the schema carries that.

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 with zero filler; the core read action and id provenance come first, and the conditional image behavior is a tight subordinate clause.

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?

An output schema exists so return values needn't be described, and the id/pagination mechanics are fully in the schema. The description covers the id source and the image-return condition, leaving only pagination behavior unmentioned in prose.

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 both artifact_id and cursor are already fully documented, including the id shape and the cursor round-trip rule. The description only adds provenance for ids, 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?

States a specific verb+resource ("Read a project source or creation") and scopes it to the studocu:// id form, with the originating tools named. It does not explicitly differentiate itself from the sibling read-detached-document, which an agent could confuse it with when deciding what to read.

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?

It tells the agent exactly where a valid artifact_id comes from (get-project-state, add-document-sources, write-artifact, request-creation), which is the practical precondition for calling it. There are no explicit exclusions or pointers to alternative read tools, so not a 5.

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