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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavioral context: it is public, requires no auth, returns third-party copy verbatim, and explicitly warns agents to quote it rather than treat it as instructions. It also explains the payout cadence and the broader earning workflow. No contradiction exists.

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 a dense, all-caps paragraph with long parentheticals, promotional asides, and multiple stacked clauses. It front-loads the core subject but packs too much tangential detail into one block, making it harder for an agent to scan and extract the essential information quickly.

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 no-argument, read-only briefing tool with no output schema, the description is comprehensive: it covers the brief content, sponsor ranks, payout rules, the X account proof flow, Solana payout address, Friday revenue split, the data-safety warning, and public/no-auth access. Nothing necessary for correct invocation 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 has zero parameters and schema description coverage is 100% because the schema is empty, so parameter documentation is not needed. The description adds value by explaining what the returned brief will contain, which is the only meaningful semantic context for a no-argument tool.

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 that the tool provides the live Wall sponsors, their copy, links, images, X handles, and the payout rules, so an agent can tell it is a read-only promotional briefing. It lacks an explicit action verb like 'lists' or 'returns' and does not differentiate itself from sibling tools such as adnet_feed or wall_mcp_publish, so it falls short of a 5.

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 gives strong contextual usage guidance: it positions this as 'the earning half of Rokha,' explains when to promote a sponsor from a proved X account, and references x_link_start/x_link_verify for account proof and GET /api/promo/topics for the full topics brief. It does not explicitly state when not to use the tool or compare it to sibling ad/ads tools, so it is not fully explicit.

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