rynmesh_list_clips

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

With no annotations, the description carries the burden of disclosing behavior. It does indicate a read-only listing operation and a scope ('visible to this node'), which is useful. However, it does not explain what 'signed clip announcements' implies, what 'compatibility' means, how invalid entries are handled, 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?

The description is a single concise sentence with no unnecessary elaboration. The 'Compatibility tool' prefix is slightly vague but does not add significant bloat. Overall it is well-structured and front-loaded with the action.

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?

Given the lack of annotations and output schema, the description leaves important gaps: what counts as a 'signed clip announcement,' what 'compatibility' means, how 'include_invalid' changes results, and how this tool relates to the many sibling list tools. An agent would likely need additional context to invoke it confidently.

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 mention the 'include_invalid' parameter at all. The parameter name gives some hint that invalid items may optionally be included, but the description does not clarify its effect, default behavior, or interaction with 'signed' announcements.

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 states a specific verb and resource: 'list signed clip announcements visible to this node.' This distinguishes it to some degree from sibling tools like rynmesh_list_peer_clips by emphasizing node-local visibility. However, the phrase 'Compatibility tool' is vague and adds little precise meaning.

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?

There is no explicit guidance on when to use this tool versus alternatives such as rynmesh_list_peer_clips or rynmesh_list_content. The 'Compatibility tool' label hints at a specific context, but no conditions, exclusions, or alternative routing are provided.

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