search_standalone_roles

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

The annotations already mark this as read-only, and the description adds meaningful behavioral details: the tag parameter uses only the first comma-separated segment, and a v1-unsupported error may occur if public Galaxy is unavailable. This goes beyond annotations without contradicting them.

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 compact, front-loaded with the core purpose, and every sentence adds information about scope, alternatives, tag behavior, or failure conditions. There is no filler.

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 search tool with two parameters, an output schema, and a clear sibling context, the description provides sufficient guidance: scope, alternative tool use, tag handling, and an edge-case error. The agent can reliably invoke this tool without additional clarification.

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 100%, so the schema already documents both parameters. The description adds a small amount of context for tags, but most of that behavior is also captured in the schema itself.

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 opens with a specific verb and resource: 'Search Galaxy standalone/legacy roles by keyword.' It also distinguishes itself by explicitly separating standalone (2-part) roles from collection roles.

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 clearly states that collection roles should use search_collections/get_role_doc instead, giving a direct alternative. It also warns about the v1-unsupported error condition, helping the agent decide if this tool will work in the current environment.

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