creatives_get

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

The description discloses the read-only nature ('Fetch') but lacks additional behavioral details such as error handling, response structure, or any side effects. With no annotations, the description carries the full burden, which it does not meet.

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 concise with a single sentence, but it could include more useful information without becoming verbose. It is front-loaded but leaves out context that would help the agent.

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 no output schema and minimal description, the tool fails to explain what the response contains (e.g., full creative details, subset of fields). It also does not differentiate from siblings effectively, leaving the agent with gaps.

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 description does not add meaning beyond the input schema. The schema covers 50% of parameters with descriptions (only orgId). The description fails to explain that 'by ID' refers to creativeId or clarify the purpose of orgId further.

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 verb 'Fetch', the resource 'a single creative', and the identifier 'by ID'. This distinguishes it from sibling tools like creatives_list and creatives_find, which have different purposes.

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 explicit guidance is given on when to use this tool vs alternatives. While the description implies using it when you have a known creative ID, it does not mention when not to use it or suggest alternatives like creatives_list for browsing.

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