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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful constraints beyond that: access is limited to an "active" share and no private source access is granted. It says nothing about the shape or size of what 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?

Three short sentences, front-loaded with the purpose, then parameter sourcing, then the downstream workflow hint. Every sentence carries information; only "bounded metadata" is vague filler-ish.

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 with annotations and no output schema, the definition covers when to call it and access limits. However, with no output schema the description never hints at what fields are returned, leaving the agent guessing what "bounded metadata" contains before it decides to save a copy.

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% and already documents the 32-hex-character format; the description only adds where to find the value (the /s/<share_id> link). That is a minor addition over the schema, consistent with the baseline 3 for fully documented single-parameter tools.

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 and resource ("read bounded metadata for an active shared score") and the qualifier "active" narrows scope, distinguishing it from siblings like get_score, get_score_share and save_shared_score. What counts as "metadata" is left unstated, keeping it short of a 5.

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 a concrete entry condition (use the share_id from the /s/<share_id> link) and a workflow cue ("read its current edition_id before saving a copy"), implicitly routing the agent to save_shared_score. It doesn't explicitly name alternatives such as get_score_share, so no full 5.

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