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

With no annotations provided, the description must carry the full burden. It mentions it is 'Fast' and implies it returns narrative text, but it does not disclose specifics like auth requirements, potential side effects, or failure modes. It also warns that a Dex handle is not a thesis, which hints at input limitations, but overall it lacks thorough behavioral disclosure.

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 concise and front-loaded with the core purpose. It includes a few imperative fragments ('Fast. Desk/open/wire already stamp a cached story.') that add value but could be more structured. Overall, it is efficient with no redundant text.

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?

Given the lack of annotations and output schema, and four parameters with zero schema coverage, the description does not provide enough context for full correct invocation. It omits the return format, error conditions, and the role of non-required parameters, making it insufficient for an agent to confidently use it in all scenarios.

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 0%, so the description must explain parameters. It only indirectly clarifies that 'symbol' is the named ticker (via 'Use this for a named ticker') and implies the tool fetches narrative for that ticker. The other parameters (name, address, quoteSymbol) are not explained at all, leaving significant ambiguity in how they affect the tool's behavior.

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's purpose: it provides the narrative for a new token, including the tweet or site thesis and purchaser info. It distinguishes itself from siblings by warning 'A Dex handle is not a thesis' and noting that 'Desk/open/wire already stamp a cached story,' clarifying this is for fresh narratives on named tickers.

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?

It gives explicit usage guidance: 'Use this for a named ticker' and implies that desk/open/wire should be used for cached stories. It also warns against using a Dex handle as a thesis. However, it does not enumerate all alternatives or explicitly state when not to use it beyond the cached story caveat, so it's good but not exhaustive.

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