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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context beyond that: sections are paginated with explicit omissions, results carry exact work citations, the work revision excludes legacy memories, and questions/outcomes are contributor reports rather than verified conclusions. This trust/semantics caveat is real added value.

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?

Front-loaded with the core action and scope, then exclusions, then behavioral caveats. Three sentences with essentially no filler, though the final sentence is dense jargon ('the work revision excludes legacy memories') that could be clearer.

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, 4 parameters and complex domain semantics, the description does the heavy lifting: it lists the covered sections, names the exclusions and their own tools, and flags pagination and data-trust caveats. What is missing is sibling differentiation among get_orbit_context/timeline/revision and per-parameter detail, but for a read-only retrieval tool this is close to complete.

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 only 25%, so the description must carry more weight. It does enumerate the seven section values (matching the enum) and states that sections are paginated, which maps to page/per_page. However it gives no guidance on per_page bounds, no explanation of the section-required-when-page>1 rule, and no clarification of what 'explicit omissions' means for pagination parameters.

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 (the task-work and legacy-memory sections of a public topic), then enumerates the exact sections covered: tasks, attempts, checkpoints, memories, questions, evidence, history. It also scopes the tool by naming what it excludes and pointing to the sibling tools that cover that excluded content (search_contributions, list_artifacts), so an agent can distinguish it from alternatives without opening a 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?

Provides an explicit routing rule: use search_contributions and list_artifacts separately for revisioned contributions and stored artifacts, which tells the agent when NOT to use this tool. It does not, however, distinguish this tool from the other orbit siblings (get_orbit_context, get_orbit_timeline, get_orbit_revision), leaving that selection to inference.

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