get_subscriber

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

No annotations are provided, so the description carries the full transparency burden. It conveys a read operation via 'Get', but does not disclose additional behavioral traits such as error handling, rate limits, or the exact composition of 'detailed information'. For a simple getter 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, focused sentence that directly states purpose and input. Every word contributes, with no filler 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?

With no output schema, the description must explain what 'detailed information' includes, but it does not enumerate fields or clarify whether a missing subscriber returns an error or null. It is sufficient for a basic getter but incomplete given the lack of output schema and annotation context.

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%; the parameter is already described as 'The subscriber ID (UUID) or email address' in the schema. The description adds minimal extra meaning beyond restating that lookup is by ID or email, so it does not significantly compensate or add beyond the structured schema.

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 uses a specific verb ('Get') and resource ('detailed information about a specific subscriber'), and clearly states the lookup key ('by ID or email address'). This distinguishes it from sibling tools like list_subscribers (which lists multiple) and get_subscriber_stats (which returns statistics).

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 implies usage for retrieving a single subscriber's details, but does not explicitly state when to choose this over alternatives such as get_subscriber_stats or list_subscribers. There is no mention of exclusions or prerequisites, leaving the usage context implied rather than explicit.

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