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

With no annotations provided, the description carries the behavioral burden and explicitly discloses the operation is read-only and free. This covers side effects and cost, though it does not mention authentication or rate limits—minor gaps for a zero-parameter 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?

Two concise sentences front-load the core purpose and then add the most decision-relevant details: the notify_* toggles and the free/read-only nature. There is no filler or repetition.

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, zero-parameter read operation, the description provides enough context: what resource is read, what notable settings are included, and the side-effect/cost profile. It does not describe the exact return shape, but no output schema exists and the tool name makes the return obvious.

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 tool has zero parameters, so the empty schema already fully documents the input surface. The description adds no parameter-specific detail, but none is required.

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 clearly states the tool reads CRM settings and even specifies the notify_* toggles as part of what is exposed. The verb 'Read' cleanly distinguishes it from the sibling crm_update_settings and other CRM getters.

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/write distinction is clear from the description, making it obvious when to call this versus crm_update_settings. 'Read-only, free' also signals that this is the safe, no-cost option, though it does not explicitly name alternatives.

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