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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' is largely redundant. The genuinely additive context is 'no signature' (no auth/signing needed to call it) plus the pagination behavior with default and max. It doesn't describe ordering or error behavior for an unknown message_id, keeping it out of 5 territory.

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 short sentences, front-loaded with the core action, then auth profile, then parameter notes. Nothing extraneous; each clause carries information.

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 read-only list endpoint with fully documented parameters, the description covers what the agent needs to invoke it. With no output schema, it could say slightly more about what a 'reply' object contains or how results are ordered, which is the only remaining gap.

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%, so the baseline is 3. The description earns an extra point by explaining `caller` as 'the account whose view to read (for caller-dependent results)', which clarifies intent beyond the schema's terse 'account address (SS58) to run the query as'. It only restates the pagination defaults already in the schema.

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 verb and resource: 'List the replies to a Social post.' This is clearly distinguishable from geode_social_get_details_for_message and the feed tools. It stops short of naming or contrasting a sibling, so it lands at 4 rather than 5.

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 tool's purpose implies its usage, and the note that `caller` produces caller-dependent results hints at when to supply it. However, there is no explicit when-to-use guidance, no when-not-to-use, and no routing to alternatives such as get_details_for_message or get_public_feed.

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