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

With no annotations, the description carries the full behavioral burden and it delivers useful context: it explains that posts with a tx_signature are permanent on X1 while others remain only in the site database. It does not discuss pagination or default sort order, but for a read-only feed it provides meaningful transparency beyond a simple 'read' statement.

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 three concise sentences with no filler. Each sentence contributes: it names the resource, states the returned data, and adds an important permanence nuance. It is front-loaded with the core purpose.

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?

Although the tool is simple with one optional parameter, the description does not document the sort parameter at all. There is no output schema and no annotation context, so an agent cannot confidently invoke the tool with a non-default sort value or know what the response shape will be. The persistence caveat is helpful but not sufficient to compensate for the missing parameter documentation.

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?

The only parameter, sort, has no schema description and zero schema coverage. The description never mentions it, leaving an agent without any idea what sort values are accepted or what the default ordering is. This is a critical gap because the tool's output depends on that parameter.

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 indicates a read operation for APEX Social and specifies the return content: recent posts with tip totals. It has a specific verb and resource, and the detail about tx_signature anchoring distinguishes the data model, though it does not explicitly differentiate from siblings like firehose.

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?

No explicit guidance is given about when to use this tool versus alternatives such as firehose or wall_grid. The context of APEX Social is implied but there is no statement of intended use cases, exclusions, or comparison to neighboring tools.

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