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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral disclosure beyond that: the list secret is never returned, which tells the agent a sensitive field is redacted, and it enumerates the readable field set. It does not cover permissions or rate limits, but for a simple getter this is above baseline.

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 short sentences of substance plus a compact API path reference; the field enumeration is front-loaded and nothing is wasted. The trailing 'GET /v2/list/getProps' is marginally redundant but functions as a useful mapping to upstream docs.

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?

With no output schema, the description carries the burden of describing the return shape, and it does so by listing the field categories returned plus the one field deliberately omitted. For a one-parameter read-only getter, an agent has enough to select and call it correctly; only permission/pagination-style concerns are unaddressed.

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% and the single parameter already documents itself ('NewsMAN list id (from newsman_list_lists)'). The description adds nothing about the id (accepted types, format, where to obtain it), so the baseline 3 applies.

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 names a specific resource ('properties of one list') and enumerates the concrete fields returned (sender name/email, owner contact, site, link parameters, send rate), which makes it clearly distinguishable from the sibling list-enumeration tool newsman_list_lists. The retrieval verb is implied by 'Properties of' rather than stated, but the scope is unambiguous.

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?

Usage is implied rather than stated: the reader can infer this is for inspecting a single known list, and the schema points back to newsman_list_lists as the source of the id. However, there is no explicit when-to-use/when-not guidance or comparison against related getters like newsman_get_list_growth or newsman_count_list_subscribers.

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