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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description adds the non-obvious side-effect guarantee that no project source is created, which is meaningful beyond readOnly. It does not cover document size limits, pagination, or failure modes, so it stops short of 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 capability and its scope constraint front-loaded ahead of the sibling reference. Every sentence earns its place by disambiguating from read-artifact.

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 single-parameter read tool with full annotation coverage and an output schema, nothing essential is missing: the agent knows what it reads, that it won't mutate project state, and which sibling to use instead. Return values are already handled by the output schema.

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?

Only one parameter and schema description coverage is 100%, so the schema fully documents document_id, including its positive-integer bound. The description's only parameter-adjacent signal ('without creating a project source') restates the same concept, adding no syntax or format detail beyond the schema. Baseline 3 for a schema-does-the-work case.

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 (read) and resource (a Studocu document) plus the defining scope condition: no project source required or created. It explicitly separates itself from the sibling read-artifact, so an agent can choose between them without opening either schema.

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?

Gives the selecting condition directly ('without requiring or creating a project source') and names the alternative tool with its own condition ('Use read-artifact for documents attached to a project'). This is an explicit when/when-other routing rule, not implied guidance.

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