Get Ad Creative Details

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description's 'Gets' is consistent but adds no new behavioral context (e.g., required permissions, error behavior, return structure). It adds minimal value beyond the annotations.

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 and front-loaded with the main action. The parameter list is redundant with the schema but doesn't harm clarity. It is short and efficient, earning a high score for conciseness.

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?

With no output schema, the description doesn't describe what data is returned (fields, format, etc.) or mention the response_format parameter. It also doesn't clarify how this tool differs from meta_get_ad, leaving an agent under-informed. For a simple get, more detail is expected.

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 schema covers only one parameter (response_format) with a description; creative_id lacks a schema description. The description's Args section repeats 'Creative ID' without adding insight into its meaning, source, or constraints. With 50% schema coverage, the description fails to compensate for the missing documentation.

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 it 'Gets detailed information about a specific ad creative', using a specific verb and resource. This distinguishes it from listing (meta_list_ad_creatives) and creation (meta_create_ad_creative), though it doesn't specify what 'detailed' includes, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives like meta_list_ad_creatives or meta_get_ad. It implies retrieval by ID but doesn't state conditions, exclusions, or how it differs from similar tools.

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