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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive, so the safety profile is fully covered. The description adds the HTTP method and endpoint path, which is useful route context but not richer behavioral detail like rate limits or response shape, so 3.

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?

Single sentence, front-loaded with the core purpose and context, and no redundant words. Highly efficient.

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 two-param read tool with rich annotations, the description covers purpose, use context, and endpoint. However, with no output schema it does not describe what the 'deep profile' contains, and parameter semantics remain thin, leaving some gaps.

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%, so the description must compensate. It maps chain and address to path segments via ':chain/:address', implying they are identifiers, but gives no examples of valid chain values or what address represents, adding only partial meaning.

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 ('one meme coin') and operation ('deep profile') plus context ('before a buy decision (risk/market)'). The phrase 'one meme coin' implicitly distinguishes it from the plural memeswap_tokens list tool, but no sibling is named explicitly, keeping it at 4.

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?

Provides a clear use context: run this before a buy decision for risk/market analysis. It does not name alternatives (e.g., memeswap_tokens for listing) or exclusions, but the when-to-use is explicit, matching a 4.

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