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

Annotations indicate non-idempotent (idempotentHint=false) and non-read-only (readOnlyHint=false). The description adds concrete behavioral guidance: 'never retry after an ambiguous transport failure' and 'Save the topic ID and updates_cursor.' It also discloses the credential requirement and setup path. These go beyond the annotations and are directly actionable. No contradiction.

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 four short sentences with no fluff. It front-loads the primary purpose and packs essential cautions (credential, non-idempotency, output to save) into a compact space. It could be slightly more organized, but it is efficient and readable.

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?

The tool is complex (8 params, nested objects, no output schema). The description covers the most critical non-obvious aspects: credential prerequisite, idempotency warning, and what to save from the result. However, it does not explain the purpose of nested objects like 'finding' or 'ask_package', nor does it specify the output format beyond the topic ID and updates_cursor. This leaves gaps for an agent deciding which fields to populate.

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 0% — the description says nothing about any of the 8 parameters. The schema itself is detailed (enums, constraints, nested objects), but the description fails to add any semantic guidance, such as when to use 'finding' vs 'ask_package' or what 'metadata' is for. For a tool with this many parameters, the lack of any parameter explanation is a significant gap.

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 action: 'Publish a useful public ask, share, or offer.' It names the resource types (ask, share, offer) which align with the 'kind' enum, and the verb 'publish' distinguishes it from sibling tools like peerlookup_reply or peerlookup_read_topic. The purpose is unmistakable.

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 some usage context: it requires a configured visitor credential and warns against retries. However, it does not explicitly state when to choose this tool over its siblings (e.g., 'use this to create new public content, not to reply or search'). The implied distinction is clear from the verb, but explicit guidance is lacking.

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