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

With no annotations provided, the description carries the behavioral burden and discloses important traits: access is limited to the active Coach-Token owner and explicitly granted materials, drafts and current revisions are included, and staff/global site access is excluded. It also describes how returned text should be treated. It omits pagination and return-format details, though an output schema exists.

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?

The description is front-loaded with the core listing behavior and then adds access exclusions and data-handling guidance. It is appropriately sized, though the first sentence is dense and could be slightly clearer.

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?

The description covers the tool's access scope and content inclusion well, and the output schema removes the need to explain return values. However, it leaves the required token parameter unexplained and does not help the agent choose this tool over nearby siblings, so it is only adequately complete.

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 has zero description coverage for the single required 'token' parameter, and the description never explicitly explains the token's format or role. 'Coach-Token owner' gives weak contextual inference, but the parameter itself remains largely undocumented.

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 states a specific verb ('List') and resource ('materials'), and clarifies the access scope: active Coach-Token owner plus exact operator-granted materials, including drafts and revisions. It distinguishes the access boundary with 'No staff or global site access,' though it does not explicitly route the agent against sibling tools such as online_article_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?

The description does not say when to use this tool versus alternatives like online_article_get or online_content_get. It provides an access constraint ('No staff or global site access') and notes that returned text should be treated as editorial source data, but this is not the same as explicit usage guidance.

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