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

With no annotations provided, the description carries the full burden and discloses meaningful behavioral traits: it is conservative ('unknown' over guessing), never renders a trust/scam judgment, and is explicitly not financial advice. This sets accurate expectations for how to interpret results. It omits error/rate-limit/auth details, but for a single-param read operation the key disclosures are present.

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?

Three sentences with the core purpose front-loaded. The behavioral clause ('Transparent, conservative...') earns its place as critical disclosure, and the 'NOT financial advice' disclaimer is necessary for a trust-adjacent tool. Slightly wordy but no wasted content.

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 lists the output categories (age, activity, SOL balance, SPL holdings, footprint band), which partially compensates for the absent output schema by telling the agent what to expect in the response. For a single-parameter tool with full schema coverage, the main remaining gap is the exact return format, which is minor here.

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 100% and the schema already describes the address parameter as 'Base58 Solana wallet address to profile.' The description's mention of 'Requires ?address=<wallet address>' is redundant with the schema and adds no new semantic detail (e.g., format constraints or validation behavior). Baseline 3 is appropriate since the schema does the work.

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 (Solana wallet) and action (activity profile) with enumerated output dimensions: age, transaction activity, SOL balance, SPL token holdings, and footprint band. This clearly distinguishes it from the token-focused siblings (solmachina_token_risk, solmachina_token_holders) and tx-focused tools (solmachina_tx_inspect, solmachina_verify_receipt), which profile different resources.

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 when to use it (when a wallet-level activity/trust footprint is needed) and states the address requirement, but it never names sibling tools or gives explicit when-not-to-use conditions. With 26 siblings, explicit routing guidance would meaningfully help, though the distinct purpose partially compensates.

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