get_campaign_results_by_date

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

Without annotations, the description must carry behavioral disclosure. It adds only 'Read-only' and the SOAP operation name, but omits authentication needs, rate limits, what happens with missing dates, or return format. This is minimal but not contradictory.

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 short but redundant: 'Calls GetCampaignResultsBetweenDates' and 'SOAP operation: GetCampaignResultsBetweenDates' repeat each other, and no sentence earns its place by adding actionable detail.

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 tool with four parameters (two required, one enum), no output schema, and no annotations, the description is far too sparse. It fails to explain parameter semantics, output, or when to use the tool, leaving the agent with insufficient context to invoke it correctly.

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% and the description mentions none of the four parameters—neither the required iCampaignID/eMessageStatus nor the optional date ranges—so it adds zero semantic meaning beyond the raw schema.

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 merely expands the operation name (GetCampaignResultsBetweenDates) into a sentence, restating the tool name rather than stating in plain language what the tool retrieves or how it differs from siblings like get_transactional_results_by_date. It does not clarify what 'results' means or what the output contains.

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; siblings exist and the description offers no context or exclusions. Nothing helps an agent choose between this and get_transactional_results_by_date or get_campaign_summary.

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