rynmesh_list_content

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

With no annotations, the description carries the full behavioral disclosure burden. It adds useful context by specifying the resource type ('signed content announcements') and the visibility scope ('visible to this node'). However, it does not explain what 'visible' means, how invalid entries are treated, whether the operation is read-only, or what the response contains.

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 front-loaded sentence states the action, resource, and scope with no filler or repetition. Every word contributes meaning, and it is appropriately short for such a simple tool.

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 tool has no annotations and no output schema, so the description alone must make the tool safely callable. It leaves important gaps: no usage guidance, no parameter semantics, no clarity on what counts as 'visible to this node,' and no differentiation from many content-related sibling tools.

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%, and the description does not explain the only parameter, include_invalid. The parameter name is somewhat self-explanatory, but the description adds no meaning about what 'invalid' means in this context, when to set it, or the default behavior.

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 uses a specific verb ('List') and identifies the resource ('signed content announcements') plus a clear scope ('visible to this node'). This is clear and informative, though it does not explicitly differentiate itself from closely related siblings such as rynmesh_list_content versus rynmesh_list_peer_content or rynmesh_list_clips.

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 lists locally visible content announcements but gives no guidance on when to prefer it over sibling tools like rynmesh_list_peer_content, rynmesh_list_clips, or the fetch variants. No exclusions, prerequisites, or alternative selection criteria are provided.

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