simpletexting_get_mediaGet a single media item (MMS asset) by its id, including its URL and metadata. SimpleTexting REST: GET /media/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| media_id | Yes | Media item id. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true. Description adds that it returns URL and metadata and uses GET, but no additional behavioral traits beyond annotation.
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 sentences with no fluff; front-loaded with purpose and brief REST reference.
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?
Simple tool; description covers purpose and return info. Lacks mention of error states or relationship to sibling tools, but sufficient given low complexity.
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 100% and parameter description is minimal. Description does not add extra meaning beyond schema for the media_id parameter.
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?
Clearly states 'Get a single media item (MMS asset) by its id, including its URL and metadata.' Distinguishes from list_media by focusing on a single item.
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 on when to use this tool vs. alternatives like list_media. Does not specify prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: evaluate vs send, get vs list for campaigns/contacts/media/messages, and update for contacts. No overlapping purposes.
All tools follow a consistent 'simpletexting_verb_noun' pattern with lowercase and underscores. Verbs are imperative (evaluate, get, list, send, update) and nouns use singular for get and plural for list, as expected.
11 tools is well-scoped for a messaging API, covering the core operations without being excessive. Each tool serves a clear purpose and earns its place.
Significant gaps exist: no create or delete for contacts, campaigns, or media; no delete for messages. The surface is read-heavy with only send and update as write operations, limiting full lifecycle management.