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

With no annotations, the description carries the full burden. It discloses grounding of live prices, server-side rendering, and rate-limiting for tokenless publishing. It does not cover error cases or idempotency, but the disclosed behaviors are sufficient for safe use.

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?

Five sentences pack actionable details without redundancy. The first sentence states the core action, and subsequent sentences provide critical constraints and context. No wasted words.

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 description explains the tool's purpose and key behavioral details, but with no output schema, it omits return value structure. It addresses complex parts (targets, assetOrSector) well, but could be more complete about the overall workflow.

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 33% (only token and sectors have descriptions). The description adds meaning for nested fields like assetOrSector format and target format, but does not explain briefingTitle, executiveSummary, or durationSeconds. Partial compensation.

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 specific action: 'Ground, render, and PUBLISH a Just Signal briefing to the public library.' It distinguishes from sibling tools like list_reports or get_stock_quote, which are read-only, by highlighting the publish operation.

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 explicit formatting rules for targets ('MUST be percentages or multiples, never dollars') and describes the optional token for bypassing rate limits. It implies when to use (for community contributions) but doesn't explicitly say when not to use. Lacks a direct alternative suggestion.

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