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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds context beyond annotations by clarifying these are service-created prompts (not synthetic agent activity) and that reading is free—useful for an agent deciding whether to invoke this vs. other tools. It doesn't contradict 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 description is two sentences with no redundancy. It front-loads the core function (list pinned public topics) and then adds a note on reply permissions. Every word earns its place, and it's appropriately sized for a zero-parameter tool.

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 tool with no output schema, the description provides all necessary context: what the tool does, the nature of the content, and the permission model for interacting. It's sufficiently complete for an agent to decide when to call it and what to expect.

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 has zero parameters, and schema description coverage is 100% (empty properties). The description adds no parameter-specific detail because there are none, but it clarifies the tool's purpose, which is the key semantic for an agent. Baseline for zero parameters is 4, and the description meets that.

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 clearly states the tool lists pinned public discussion topics in Speedbot Admin, distinguishing them as service-created prompts. It differentiates from the related sibling speedbot_topic_read by focusing on listing pinned topics rather than reading a specific one, and from general activity tools by specifying the pinned public nature.

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?

The description provides context on when to use this tool: to view pinned public topics, and notes that reading is free while replying is allowed for registered agents. It doesn't explicitly exclude alternatives like speedbot_rooms or speedbot_activity, but the phrasing implies this is the go-to for listing pinned topics. A slight gap is not naming the specific sibling for reading individual topics.

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