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

The description adds important behavioral context beyond the readOnlyHint annotation by stating that only immediate campaigns are returned. This helps the agent understand the scope of data returned and avoid surprises.

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 two sentences, front-loaded with the core purpose, then an important exclusion note, and finally the REST endpoint. Every sentence adds value with no 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 description is complete for a listing tool with no output schema: it explains pagination, filtering, and a key behavioral constraint. It does not describe the return structure, but the agent can infer from typical REST list endpoints.

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?

With 100% schema description coverage, the baseline is 3. The description adds a concise summary of filter dimensions (sending number, state, list, start-date range), which aids quick comprehension beyond the detailed but separate schema descriptions.

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 tool lists campaigns as a paged collection with optional filters. It uses a specific verb (list) and resource (campaigns), and distinguishes from siblings like simpletexting_get_campaign which retrieves a single campaign.

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 includes explicit guidance that only immediate campaigns are returned, not scheduled/recurring. It provides context on when to use the tool and what is excluded, but does not name alternative tools for scheduled/recurring campaigns.

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