get_social_media_drafts

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

Description provides no behavioral details beyond the name. It does not disclose that the tool is read-only, supports pagination, filtering, or sorting, nor any authentication requirements or rate limits. The schema provides parameter descriptions but the description adds no additional transparency.

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 very concise (5 words) but lacks substance. While brevity is good, it sacrifices necessary detail. The front-loaded phrase 'Get draft social media posts' is clear but does not earn its place as the sole description.

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 has 7 parameters, pagination, filtering, and no output schema, the description is insufficient. It does not explain the return format, meaning of account_ids, pagination behavior, or any prerequisites. The description is incomplete for an agent to use effectively.

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 description coverage is 100%, so baseline is 3. The description does not add any meaning beyond what the schema already provides for parameters like account_ids, tz, page, etc. It fails to explain how parameters interact or the expected format of inputs.

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?

Description states 'Get draft social media posts', which clearly indicates the action and resource. However, it does not differentiate from siblings like get_social_media_posts (presumably published posts) or other draft-related tools, leaving ambiguity about what 'drafts' specifically means in this context.

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 versus alternatives. With many sibling tools for social media (get_social_media_posts, delete_social_media_draft, etc.), the description offers no context for appropriate usage or exclusions.

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