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

With no annotations, the description carries full behavioral burden. 'Read' inplies a non-mutating operation but that is already inferable from the name; the signed-capability detail largely repeats the schema's token description. It does not disclose behavior for invalid or expired tokens, response shape, or any other operational traits.

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?

Six words, front-loaded, and no extraneous content. Every word earns its place, and the core mechanism is stated immediately.

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 operation, the description is minimally viable: it tells the agent what to pass and what action is performed. However, it does not explain how to obtain the token, what a preference represents, or what the agent should expect in response, so an unfamiliar agent would still need to infer several things.

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 coverage is 100%, so the single token parameter is already documented as 'Signed preference token'. The description adds only the phrase 'signed capability', which does not materially extend the schema's meaning.

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?

Description states a specific verb (Read) and resource (preference), plus the auth mechanism (signed capability). It is distinct enough from sibling preference_token_create and preference_unsubscribe, although it does not explicitly contrast with them.

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 prefer this tool over siblings like commsharbor_preference_token_create or commsharbor_preference_unsubscribe. It implies a signed token is needed but does not explain where that token comes from or when this tool should be used.

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