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

With no annotations at all, the description carries the full behavioral burden and does substantial work: it declares secrets are never returned, defines callBlockers' object shape and inbound/outbound scope, and bounds lastRefused to the last 7 days. It does not say whether results are paginated or whether the call is strictly read-only, leaving those traits undeclared.

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 resource and its returned fields are front-loaded in the first sentence, with the two non-obvious fields (callBlockers, lastRefused) explained after. It is dense and slightly list-heavy but every sentence conveys distinct information, with no repetition of the name back to itself.

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?

There is no output schema and no annotations, so the description has to describe the return payload, which it does field-by-field for the important ones and with object shape for callBlockers. Gaps remain around pagination, ordering, and behavior when a workspace has no lines, which matter for a list tool.

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 0% and the single required parameter workspaceId is undocumented in the schema, so the description must compensate. It only implies scoping via "this workspace's" and never names the parameter or its UUID format, leaving the agent to map the phrasing onto the schema field.

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 ("List this workspace's phone lines") and enumerates the returned fields (provider, mode, ring window, health) plus offered providers. It implies the tenant-scoped read use case, but never explicitly distinguishes itself from siblings like lines_get or platform_lines_list, which an agent could easily confuse with it.

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 only implied by "this workspace's" and by the instruction to tell the user when a callBlocker is present. There is no explicit statement of when to call this instead of lines_get (single line) or platform_lines_list (platform-wide), so the agent must infer the boundary from the sibling names alone.

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