get_bulk_sms_job

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

No annotations are provided, so the description bears full responsibility. It correctly indicates a read operation without side effects, though it could be more explicit about being non-destructive. The mention of progress implies multiple states.

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 concise: one sentence for purpose and one for parameter guidance. No extraneous information, and the key action is front-loaded.

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 the tool's simplicity (1 parameter, output schema exists), the description fully covers the necessary context. It tells what the tool returns, what input it needs, and where that input comes from.

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 0% schema description coverage, the description adds essential context for the job_id parameter: 'The job UUID returned by send_bulk_sms.' This informs the agent about the parameter's origin, going beyond the schema's title.

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 explicitly states 'Get the status and progress of a bulk SMS job,' which clearly identifies the action and resource. This distinguishes it from siblings like send_bulk_sms or list_sms_sender_ids.

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 instructs that the job_id is the UUID returned by send_bulk_sms, providing clear context for when to use this tool (after sending a bulk SMS). While it doesn't explicitly list alternatives, it effectively narrows usage.

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