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 gestures at a return-shape trait ('each is a reference') but cuts off before it explains what a reference is or what else is returned, leaving the one piece of added behavioral context unusable.

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?

Brevity here is under-specification rather than economy: the single sentence is truncated and ends on an unclosed parenthetical, so no information is front-loaded beyond a partial subject.

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 no output schema and an undocumented parameter, the description needed to explain both the returned share/reference structure and the space filter; instead it is a cut-off fragment. An agent cannot confidently call this tool correctly from the definition alone.

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?

The single 'space' parameter has 0% schema description coverage, so the description carries the burden, and it only weakly implies a space-scoping connection via 'through a space you are in'. It never explains whether 'space' filters, is required, or accepts a name vs ID.

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?

The fragment 'The document shares you hold, through a space you are in or made to you' identifies the resource (document shares) but never states a verb or the list semantics outright, and the sentence is truncated mid-thought ('each is a reference (home...'). An agent can guess this enumerates shares, but the definition never finishes saying what it does or how it differs from doc_list or my_share.

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?

No when-to-use guidance and no alternatives named, despite close siblings (doc_list, doc_read, doc_share, doc_revoke, my_share) that an agent must choose between. The 'space you are in or made to you' phrase hints at two sourcing modes but does not say which to pick or what the tool excludes.

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