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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: it discloses the nested row inheritance rule (a row without carried_by is carried by its parent's carrier) and warns that several fields are free text typed by edit-link holders and returned unchanged, flagging user-generated content. This goes meaningfully beyond the annotations.

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?

The return shape is front-loaded ('A shared list as data') and the field enumeration, though dense, is warranted given there is no output schema. The parenthetical list runs long but every clause conveys a distinct, useful fact.

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, the description must carry the return-value burden, and it does so thoroughly by enumerating the returned fields, the nesting behavior, and the free-text provenance. Input and output are both adequately covered for a single-parameter read tool.

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 only parameter is fully documented in the schema (including the 'not an edit link' warning). The description restates 'share code or share link' without adding format or syntax detail, 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?

The description states a specific resource (a shared list) and details exactly what is returned: title, unit, dates, trail, totals and folders with rows. The phrase 'as data' implicitly contrasts with the sibling get_list_markdown, but the differentiation is left for the agent to infer rather than stated outright.

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 explains what input the tool consumes ('Takes a share code or share link') but gives no when-to-use guidance and never names or rules out the obvious alternative get_list_markdown. The agent must infer which of the two retrieval tools to pick.

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