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

No annotations are provided, so the description carries the full burden. It hints that authorization and validation mirror the website/API/CLI, but never states which permissions are required, what validation is applied, or whether this is a read-only lookup — leaving the agent to infer the entire safety profile.

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 text is short, but the opening sentence is pure filler that duplicates the name, and the second sentence is vague boilerplate. Brevity here reflects under-specification rather than disciplined front-loading of useful information.

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 lookup tool with two undocumented required parameters, no annotations, and no output schema, the description supplies essentially none of what an agent needs: not the return shape, not the auth/permission requirements in concrete terms, not the failure modes. It is inadequate for the tool's complexity.

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?

Both required parameters (workspaceId, id) have 0% schema description coverage, and the description adds nothing about what they identify or how they relate. The only meaning available comes from raw type/format keywords in the schema, which the description fails to compensate for.

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 first sentence, 'SAGOT campaigns.get', merely restates the tool name and namespace without saying what the operation does (presumably fetch a single campaign by ID). It gives no distinction from siblings like campaigns_list or campaigns_preview, so an agent cannot tell what resource or scope this returns.

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 guidance on when to call this versus campaigns_list, campaigns_preview, or any other sibling, and no stated preconditions. The only context offered ('same authorization and validation as website, API and CLI') is about consistency, not about when to select this tool.

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