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

There are no annotations, so the description carries the burden of disclosing behavior. It clearly indicates a read-only operation and specifies the two pieces of information returned. It does not cover failure behavior or response formatting, but those are minor for a simple getter.

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?

A single sentence with no filler, starting with the operative verb 'Read' and then specifying exactly what is read. Every word earns its place.

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 one-parameter read tool with no output schema, the description gives enough information to call it: pass an organization ID and expect the organization timezone plus marketing paused state. It could be more explicit about return field names or error behavior, but the core call context is complete enough.

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 schema already provides 100% coverage for the single required parameter with 'Active organization ID', so the baseline applies. The description adds only that the organization's settings are being read, adding no additional format, constraints, or relationship details beyond the 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 uses the specific verb 'Read' and names the exact data returned: the organization's timezone and whether marketing is paused. This makes the tool's purpose clear and distinguishes it from the sibling write tool commsharbor_messaging_settings_update and from per-contact marketing tools.

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 read-versus-update intent is implied by 'Read', so an agent can infer when to call this tool, especially given commsharbor_messaging_settings_update as a sibling. However, it does not explicitly state when not to use it or name alternatives such as contact-level marketing status tools.

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