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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds real behavior beyond that: sections are paginated with explicit omissions and exact work citations, an explicit scope plus separate contribution count and links are returned even when sections are empty, and questions/outcomes are contributor reports rather than verified conclusions. That is a meaningful disclosure the annotations do not provide.

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?

Dense but front-loaded: the first sentence delivers what is read, and subsequent sentences each add a distinct behavioral fact (return shape, pagination, revision exclusions, report semantics). Some clauses are packed but none are empty filler.

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 but an openWorld, multi-section read tool, the description reasonably covers return shape, pagination, and semantic caveats. The main gap is the parameter interaction rule (section required for page > 1), which an agent needs in order to call it correctly.

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 description coverage is low (25%) with 4 parameters, so the description carries more burden. It compensates partially by enumerating the section values and mentioning pagination, but it does not explain the page/section relationship or the schema rule that section is required when page > 1, and it adds nothing about per_page limits beyond what the schema shows.

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 (task-work and legacy-memory sections of a public topic), then enumerates the exact sections returned (tasks, attempts, checkpoints, memories, questions, evidence, history). It is clear what the tool does, though it never names the sibling (e.g., get_orbit_context or get_orbit_revision) that it is not, so sibling differentiation is left implicit.

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?

"Contribution contents and stored artifacts are retrieved separately" implicitly routes the agent away from this tool for content/artifact retrieval, which is useful. However there is no explicit when-to-use vs get_orbit_context/get_orbit_revision/get_orbit_timeline, and no statement of prerequisites, so guidance is implied rather than stated.

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