get_subscriber

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

With no annotations, the description carries the disclosure burden. It implies a read operation via 'Get' but does not state whether it is read-only, what happens for unknown users, authentication needs, or the exact structure of returned data. Minimal behavioral context beyond the verb.

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, focused sentence that names the operation and its key outputs. No wasted words or redundancy.

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 with one parameter and no output schema. The description lists the returned categories but lacks details on error behavior, relationship to check_entitlement, or use-case boundaries. Adequate for basic selection but incomplete for confident invocation in novel situations.

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% for the single parameter app_user_id, which is described as 'The app user ID to look up.' The tool description does not add extra context about parameter usage, so it meets the baseline but adds no additional semantic value.

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 verb (Get) and the resource (subscriber info, entitlements, subscription status) for a user. It effectively distinguishes from siblings like grant_entitlement and revoke_entitlement, which are mutations, and get_offerings, which targets offerings rather than subscriber state.

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 offers no guidance on when to use this tool versus alternatives like check_entitlement. It does not mention exclusions or provide context for choosing this over siblings, leaving the agent to infer usage.

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