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

Annotations already declare readOnlyHint and openWorldHint, and the description adds valuable behavioral context: the address is never contacted, making this a passive/non-invasive lookup. It also clarifies the data source (launchpads the system indexes and SWOGE AI colony measurements). This goes beyond what annotations alone convey.

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?

A single, information-dense sentence with front-loaded scope ('what is known about an EVM wallet address') and a clear passive-safety note at the end. Every clause contributes meaningful content, and there is no filler.

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?

There is no output schema, so the description helpfully enumerates the return categories: launched tokens, deployed tokens, and colony measurements with observation counts. It does not specify the exact response shape or error behavior, but for a simple read-only lookup the listed categories plus the passive guarantee are sufficient for an agent to select and invoke it correctly.

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 100%, so both parameters are already documented. The tool description adds no parameter-level detail beyond the schema, particularly nothing about the quote flag. Baseline 3 is appropriate because the schema carries the semantic burden.

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 identifies the resource (an EVM wallet address) and the specific information returned: launchpad launches, deployed tokens, and SWOGE colony observations with counts. It does not use an imperative verb, but 'What is known about...' is an effective purpose statement. It doesn't explicitly distinguish itself from siblings like osint_lookup, but the content scope is specific enough.

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 implies the tool is for wallet intelligence queries and notes it is passive, which helps set expectations. However, it gives no explicit guidance on when to prefer this tool over siblings such as osint_lookup or scan_token, and it provides no exclusions or alternative conditions.

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