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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered structurally. The description adds nothing behavioral: no pagination semantics, no note that withdrawn TDocs are excluded by default, no indication of result volume or ordering.

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 short sentence is front-loaded and waste-free, which is good. But the brevity here reflects under-specification rather than disciplined concision: a 15-filter tool is described with only two of its capabilities, so the sentence is too thin to be genuinely concise.

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 15-parameter, zero-required filter/search surface with no output schema, the description omits the bulk of the tool's behavior (free-text search, source/company resolution, status/doc_kind/work_item filters, date ranges, cursor paging) and gives no sense of return shape. It is not adequate for the tool's complexity.

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%, so every filter is already documented in the schema; the baseline of 3 applies. The description adds no parameter meaning beyond the two filters it names ('meeting', 'agenda item'), which the schema itself documents in more detail.

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?

States a verb (list) and resource (TDocs), so the basic purpose is clear. However, 'for a meeting or agenda item' falsely implies those are the scoping parameters when the schema exposes 15 optional filters (source, spec, status, doc_kind, work_item, dates, free-text q, etc.), and it does nothing to distinguish this from the sibling search_tdocs or list_documents_documents_get.

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?

Provides no when-to-use guidance, no mention of when to prefer search_tdocs, and no stated prerequisites. The phrase 'for a meeting or agenda item' hints at a context but never explains how it differs from the other listing/search siblings.

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