get_campaign

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose 'Read-only', which is a genuine safety signal, but says nothing about authorization requirements, error behavior for an unknown iCampaignID, or what the operation returns.

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?

It is short and front-loaded, but two of the three sentences are redundant restatements of the tool name and the SOAP operation name, giving low information density per sentence.

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 simple single-parameter lookup there is no output schema, so the description should at least indicate what a campaign record contains and confirm the ID is the sole lookup key. Neither is provided, leaving the definition 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?

Schema description coverage is 0% for the single parameter iCampaignID, and the description never mentions it. It adds no meaning about where a campaign ID comes from or what format it takes, so the one undocumented parameter remains unexplained.

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 restates the tool name ('Calls GetCampaign', 'SOAP operation: GetCampaign') rather than describing what a campaign retrieval yields or how it differs from the 12 sibling tools, several of which are also campaign getters (get_campaign_details, get_campaign_summary, get_campaign_results_by_date). 'Read-only' is the only added semantic content.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer for campaign data. With get_campaign_details, get_campaign_summary, and get_campaign_link_clicks all present, an agent has no basis from the description for choosing this one.

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