conduyt_call_flow_roster

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

No annotations are provided, so the description carries the full disclosure burden. 'Get' implies a read-only operation, and 'live availability' adds useful behavioral context that the data is current/real-time. It does not mention permissions, rate limits, or return shape, but for a zero-parameter read tool the description provides moderate transparency.

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 efficient sentence with the core action front-loaded ('Get the routing roster'). Every clause contributes useful detail about contents and purpose, with 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 zero-parameter read tool with no output schema, the description is largely complete: it explains what the roster includes and its role in call-flow/ring-group configuration. It could be slightly more complete by noting whether the result is a list, pagination behavior, or whether DIDs are always present, but the core operational need is covered.

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 tool has zero input parameters, so per the scoring baseline this dimension defaults to 4. The description correctly adds no parameter detail because none exist.

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?

States a specific verb and resource: 'Get the routing roster'. It adds distinguishing detail that the roster contains 'members with DIDs and their live availability' and is specifically for 'call-flow and ring-group steps'. This helps separate it from generic user/contact listing tools, though it does not explicitly name a sibling alternative.

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?

Usage is implied by the phrase 'the people call-flow and ring-group steps can ring', which signals the context in which this roster is relevant. However, there is no explicit when-to-use guidance versus related tools such as conduyt_list_users or conduyt_list_ring_groups, and no exclusions are stated.

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