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

With no annotations, the description carries the behavioral burden and usefully discloses that access requires administrative read authorization, that ordinary teacher tokens are denied, and that returned badge HTML is untrusted editorial data. It also indicates a read-only operation via 'Read', though it does not cover pagination, error behavior, or exact response structure.

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 three tightly packed sentences with the core purpose front-loaded and no wasted wording. Each sentence adds distinct value: purpose, authorization constraint, and a data-trust warning.

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 two-parameter read tool with no output schema and no annotations, the description gives the important context: what is returned, who can access it, and that embedded HTML is untrusted. Minor gaps remain around exact response shape and parameter details, but the critical operational caveats are present.

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 0%, so the description must compensate. It indirectly clarifies that coach_id refers to an existing coach and that token must be an administrative read token, but it does not explicitly define either parameter's format or constraints.

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 uses a specific read verb and identifies the exact resource: one existing coach's ordered external-platform profile lists, including version, draft, and published lists. This distinguishes it clearly from the sibling write operation online_teacher_profiles_set and from broader content-read tools.

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 intended use is implied by 'Read one existing coach's...' and the administrative authorization note, but there is no explicit when-to-use guidance or comparison to alternatives such as online_teacher_profiles_set. An agent can infer the use case but must still reason about when this tool is preferred.

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