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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds the underlying endpoint (GET /numbers/campaigns), which is useful provenance, but says nothing about pagination, result volume, or account scoping for what is implicitly a full listing.

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?

Two compact sentences with the purpose and scope front-loaded, followed by endpoint provenance. No filler, no restatement of the title, and every clause 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?

For a zero-parameter read-only list tool with no output schema, the definition covers what is returned (campaigns plus their status) adequately. The only omission is whether results are paginated or bounded, which is a minor gap given the tool's simplicity.

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?

The tool takes zero parameters, so per the rubric the baseline is 4 and there is nothing the description needs to compensate for. No parameter-level detail could add value here.

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 gives a specific verb+resource ("List the account's 10DLC campaigns") and helpfully glosses the jargon as "US SMS use-case registrations" with explicit status reporting. However, it offers no differentiation from closely related siblings such as notifyre_list_brands or notifyre_list_sms_numbers, so an agent must infer where 10DLC campaigns sit in the registration hierarchy.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The presence of notifyre_list_brands (a directly related 10DLC registration resource) makes the absence of routing guidance a real gap rather than a trivial one.

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