How to contribute

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely new context: the tool reports conversation-specific state (whether this assistant is connected to a GitHub account), signaling the answer can vary per session rather than being static documentation.

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?

A single front-loaded sentence with a colon list of covered topics, followed by a short imperative call-to-action. No filler or repetition; every clause carries information.

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 zero-parameter, read-only knowledge tool with no output schema, the description gives everything an agent needs: what it returns (four named topic areas) and when to invoke it before contributing or reviewing. Nothing material is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The enumerated topic list is the only meaningful content the description could add here, and it does so.

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 (contribution guidance for The Intelligence Radar) and enumerates the exact topics it covers: what can be contributed, reviewer requirements, review/publication flow, and GitHub account connectivity. The scope qualifier 'from this conversation' is useful, though it never names a sibling such as about_radar or prepare_contribution to sharpen the boundary.

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?

'Call it before helping someone contribute or review' gives a clear trigger condition and an implied ordering relative to the contribution workflow tools. It does not state when this tool is unnecessary (e.g., once the user has already read the guidance) or name alternatives for adjacent questions.

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