mc_getCampaign

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

No annotations provided, and the description omits any behavioral traits. It does not state that the tool is read-only, what requires authentication, or any constraints. The description carries the full burden but fails to disclose even basic safety hints.

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?

Extremely concise (4 words), but this brevity sacrifices clarity and completeness. It could benefit from a sentence about scope or returned data without becoming verbose.

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 get-by-ID tool, the description is minimal but lacks information about the response, any prerequisites, or error conditions. With no output schema, the agent is left guessing what 'details' means.

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 coverage is 100% with a clear parameter description for campaignId. However, the tool description adds no additional semantic value beyond the schema, missing an opportunity to clarify the parameter's expected format or source.

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 'Get campaign details' clearly identifies the verb and resource. It distinguishes from siblings like mc_listCampaigns and other get tools by specifying 'campaign', but doesn't elaborate on what 'details' entails.

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 like mc_listCampaigns (for listing) or other entity-specific get tools. The agent must infer context from the name alone.

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