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

Annotations already state readOnlyHint=true, openWorldHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds a conditional access rule (who can see per-cycle reports vs. cycles_count), which is useful behavioral context. However, it omits any rate-limit, pagination, or error behavior, and the mention of signing the request is vague.

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 first sentence is a giant run-on enumerating fields, and the second paragraph mixes access rules with raw HTTP paths and query parameters. It is not front-loaded and contains information (HTTP endpoints) that does not help an agent invoking this MCP tool. The structure would confuse rather than guide.

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 read tool with no output schema, the description should focus on what is returned and any special behaviors. It does list many fields but then diverts into HTTP endpoint syntax, and it leaves key questions unanswered: does agent_id change the response shape? What is the default for agent_id (self)? The completeness is undermined by poor organization.

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 100%, so the schema already documents both parameters. The description implies campaign_id identifies the campaign and agent_id controls report visibility, but adds no syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Read one campaign') and lists the return fields. However, despite a long enumeration, it doesn't explicitly contrast with sibling tools like get_team or list_tasks, and the final jump to HTTP endpoints adds noise rather than clarity.

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. The permission sentence implies a condition (being a party to the project) but doesn't say what to do otherwise. The mention of other HTTP endpoints does not provide 'when-to-use' routing for the agent.

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