get_blist

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

The description discloses no behavioral traits beyond what annotations already state (readOnlyHint=true, destructiveHint=false). It doesn't mention required authentication, what data is returned, pagination, or any side effects. The 'WhiteLabel' hint is too vague to be useful for understanding runtime behavior.

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 extremely short with no fluff, so it is concise in length. However, it is under-specified; the single sentence provides an endpoint but fails to define the tool's purpose or behavior. It is not structured to front-load important details because it lacks them entirely.

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 that there is no output schema and the schema has only partial descriptions, the description carries the burden of explaining what the tool returns, when to use it, and how it relates to sibling tools like create_blist/update_blist. None of that is provided, making the tool contextually incomplete for an agent.

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 only 50% (dry_run has a description, blist_id does not). The description itself adds no meaning to the parameters; it doesn't explain what blist_id is or how dry_run interacts with the request. With low coverage, the description should compensate, but it remains silent.

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 identifies the tool as 'GET /api/v2/blist' which gives a specific verb and resource, but it lacks a plain-language statement of what the tool does (e.g., retrieves a blacklist entry). The 'WhiteLabel (Python SDK parity)' note is tangential and doesn't clarify the function. It is distinguishable from siblings mainly by the endpoint name, not by described purpose.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_overview' or 'search_stop_list'. The description mentions 'Python SDK parity' but that doesn't help an agent decide between tools. There are no prerequisites, exclusions, or alternative suggestions.

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