get_archived_advertiser

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Get details,' providing no information about error behavior, permissions, or return payload characteristics beyond the generic implication of a read operation. This is minimal disclosure for a tool that may return null or throw if ID is not found.

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 a single, clear sentence with no filler. It is appropriately sized for a simple getter and front-loads the primary action and resource.

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?

For a one-parameter read tool, the description is adequate but lacks explicit information about the returned details or potential error conditions. Since there is no output schema, the description could have elaborated on what 'details' includes or any constraints, making it slightly incomplete.

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 fully covers the single parameter 'id' with a description ('Archived advertiser ID'). The description adds no extra semantic detail beyond what the schema provides, but the baseline of 3 applies because schema coverage is 100%.

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 action ('Get details') and the resource ('specific archived advertiser'). It distinguishes this tool from siblings like 'get_advertiser' (presumably active) and 'list_archived_advertisers' by emphasizing a single archived advertiser.

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 phrase 'specific archived advertiser' implies that this tool is for retrieving one archived advertiser by ID, contrasting with listing operations. However, no explicit guidance is given about when to prefer this over 'get_advertiser' or how it complements 'unarchive_advertiser'.

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