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

The description is consistent with readOnlyHint=true and adds the scope of what is read (campaigns and notice receipts) plus a separation boundary for dispatch/authorization. It does not contradict annotations, but it also does not disclose details like response shape, pagination, or any unusual behavior.

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 compact: one clear sentence followed by a short operational note. The second sentence is cryptic and could be clearer, but no word is wasted overall.

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 zero-parameter, read-only tool, this description is largely sufficient: it names the resources, implies the operation, and hints at operational boundaries. The lack of an output schema and the unexplained 'notice receipts' term keep it from being fully complete, but the call is trivial to invoke.

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?

The input schema has zero parameters and schema description coverage is 100%, so there is nothing for the description to add about parameter meaning or formatting. With 0 params, the baseline is 4 and the description does not need to compensate for any schema gaps.

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 states a clear verb and resource: 'Read your campaigns and notice receipts.' It is more specific than a bare name and aligns with the readOnlyHint. However, it does not explicitly distinguish itself from the many sibling read_* tools, and the second sentence about operational controls muddies the primary purpose slightly.

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?

The phrase 'Dispatch and campaign authorization are separate operational controls' implies that dispatch and authorization require different tools, but it never names the alternatives (e.g., authorize_campaign or approve_notice). Usage context is implied rather than explicitly stated, so an agent must infer when to use this tool versus siblings.

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