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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the payload is a transcript of a foreign author's reel plus structured essence fields, which is valuable since no output schema exists. It does not mention cost/credit consumption (relevant given the credit_history sibling) or what happens if a reel has no transcript yet.

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 tightly packed sentences with no filler: the payload description comes first, then the argument source, then the disambiguation. Every clause earns its place and the most decision-relevant information is front-loaded.

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 single-argument read tool with annotations covering safety and no output schema, the description supplies the return content, the argument provenance, and sibling disambiguation — essentially everything needed to call it. Minor gaps remain around credit cost and failure modes (missing/unprocessed transcript), but nothing blocking.

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 0%, so the description must carry the meaning, and it does partially by stating that reel_id originates from query_reels — a real semantic hint not in the schema. However it says nothing about the identifier's format or validity, so the agent still infers everything about the value itself.

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 specific verb+resource: the speech transcript of a single reel by ANOTHER author from the corpus, plus the extracted essence (topic, hook, key phrases, CTA). It also explicitly distinguishes itself from the sibling analysis_get, so an agent can separate the two without opening either schema.

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?

Gives an explicit prerequisite route for the required argument ("reel_id берётся из query_reels"), which tells the agent which tool to call first. It also names the confusing alternative (analysis_get = your own analysis) and the condition that distinguishes it, so both when-to-use and when-not-to-use are covered.

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