faceit_getHubRoles

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as authorization requirements, error handling for invalid hub_id, rate limits, or the structure of the returned roles list beyond 'Roles list'.

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 concise with three sentences and a parameter list. It is well-structured and front-loaded with the purpose. The parameter list could be integrated more smoothly, but it is not overly verbose.

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 absence of an output schema, the description only says 'Returns: Roles list', which is insufficient to understand the returned data structure. Additionally, it lacks details on typical use cases or relationships to other hub tools. For a tool with 3 parameters and no output schema, more context is needed.

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%, but the description compensates by detailing all three parameters with types, constraints (e.g., offset min 0 max 1000, limit min 1 max 50), and explanations of their meaning (starting position, number of items). This adds value beyond the schema, which only provides titles and types.

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?

Description clearly states 'Retrieve all roles members can have in a hub' and specifies 'list the roles that members of a hub can hold (admin, member, etc.)', which uses a specific verb and resource and distinguishes it from sibling tools like faceit_getHubMembers or faceit_getHubLeaderboards.

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 states 'Use to list the roles...' but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or restrictions beyond the required hub_id.

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