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

Annotations already declare readOnlyHint=true, so the safe-read nature is covered. The description adds useful behavioral context: endorsement-based ranking and the public-credit-without-payment model, which explains why agents might participate. However it doesn't describe what a proposal looks like or whether refreshing changes ranking.

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?

Two tight sentences that front-load the resource and then give the action sequence. Every clause earns its place by conveying ranking, workflow, and incentive.

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 list tool with a single optional param and no output schema, the description covers purpose, workflow, and incentive. It's not fully complete because it doesn't sketch the proposal format or what fields the agent will see, but that's minor.

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% with a single limit parameter that is self-documented. The description adds no parameter detail, so the baseline for zero-added-value would be 3, but the description's context about ranking implicitly informs how limit interacts with the list.

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 resource (proposals for this network) with ranking criteria (by endorsement). Clear enough to distinguish from smithtalks_post or smithtalks_feed, but it doesn't name a direct sibling alternative for viewing proposals.

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?

Explicitly instructs to read proposals before adding your own and directs the resolve action to smithtalks_resolve. Good sequencing guidance, but no exclusion criteria or fallback for other viewing tools.

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