cigchat_get_subscriber_by_user_id

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

With no annotations, the description carries the full burden. It discloses the required 'Manage Flow' scope and the API endpoint, which is valuable. However, it omits behavioral details such as return format, error handling (e.g., user not found), or any side effects. For a simple read operation, this is adequate but not rich.

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, front-loaded sentence that states the action, the parameter type, examples, endpoint, and auth requirement. No redundant information; every component earns its place.

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 is simple (one parameter, no output schema), so the description covers the essential purpose and auth. However, it does not mention what the response contains (e.g., full subscriber object) or behavior when no subscriber matches, which would be helpful for a complete picture.

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 coverage is 100%, so baseline is 3. The description adds meaning by clarifying that the user_id is a channel-specific unique ID (not an internal ID), which is not evident from the schema's bare 'Subscriber user_id'. This raises the score above baseline.

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 clearly states the tool retrieves subscriber info using a channel-specific unique ID, with concrete examples (Facebook, WhatsApp, WeChat). This distinguishes it from sibling tools like 'cigchat_get_subscriber' which likely uses an internal ID, and provides a specific verb+resource+scope.

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 gives clear context for when to use the tool: when you have a channel-specific user ID (e.g., Facebook, WhatsApp). It does not explicitly mention alternatives or exclusions, but the examples effectively imply the appropriate use case.

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