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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value by disclosing that cross-workspace public shares are included and that no network fetch happens, but it stops short of describing result shape or any visibility edge cases beyond the share-ID scope.

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 short sentences with zero filler; the positive scope is front-loaded and the negative constraints follow as a compact caveat. Nothing repeats structured fields verbatim.

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?

With one required parameter, full schema coverage, complete annotations and an output schema, the description supplies the scope and the two boundary conditions an agent needs. It is nearly complete; only the absence of routing guidance against sibling tools keeps it from a 5.

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 the shareId property description is unusually rich (UUID from /minds/shared/{shareId}, not the Mind ID, must be public or link-enabled, excluded fields). The description only echoes 'by share ID' and adds no syntax or format detail beyond that, 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 and resource ('Returns stored public Mind sources/assessments') plus the keying mechanism (share ID) and a scope qualifier (includes shares outside the private workspace). No sibling tool covers the same resource, so an agent can distinguish it without further reading, though the description never names a contrasting sibling.

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?

Usage is implied by the scope statement and by the two exclusions ('Does not fetch source websites or modify knowledge'), which help an agent rule this tool out for live-site retrieval or writes. It never states when to prefer it over an alternative or what precondition must hold, leaving the agent to infer routing.

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