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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's added value is ordering ('oldest first'), pagination via offset, the fact that the response states the full count, and the GitHub-role enrichment. That is meaningful context beyond the annotations, though response shape and error behavior are not described.

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 resource and its contents, followed by pagination and usage sentences. Dense but efficient; the trailing 'Canton-specific.' adds little beyond what the name already implies.

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?

For a read-only, paginated discussion fetcher with no output schema, the description covers contents, fields returned, ordering, pagination, and purpose. An agent has everything needed 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 coverage is 100%, so kind, limit, number, and offset are all documented in the schema. The description only adds 'Pages with offset,' matching what the schema already says; baseline 3 is appropriate.

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 ('The conversation on ONE Canton Dev Fund proposal') and enumerates exactly what it contains: comments, formal reviews with verdicts, and inline review comments, each with author, GitHub role, date, and text. The 'ONE proposal' scoping and canton-dev-fund specificity separate it from generic siblings like get_discussion or get_github_discussion.

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?

Gives a clear use case: 'Use to read what reviewers, champions and the committee actually said, or why a proposal stalled.' That tells the agent when this is the right tool, but it does not explicitly name alternatives (e.g., get_proposal for metadata, get_proposal_milestones) or state when not to use it.

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