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

Beyond the annotations, it discloses that the call is free, fetches nothing anew, and returns numbers as of the original analysis date, with an instruction to mention that date. This staleness and cost context is meaningful behavioral guidance not present in the structured metadata.

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 dense but front-loads the core purpose and then the content coverage and alternatives. It is somewhat compressed into a single paragraph, but nearly every clause adds value.

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 explaining return content, and it does so by enumerating the kinds of data returned (niche reels and accounts, subreddits with rules and top posts, account pieces, a reel). It also covers cost, freshness, and alternatives, leaving no major gap for correct invocation.

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 100% and both parameters are already documented, so the description only implicitly reinforces that researchId comes from list_research. It adds little beyond the schema for workspaceId or the identifier format, matching the baseline for full schema coverage.

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 (retrieve/read) and resource (a past analysis result) and scopes it to analyses the brand already ran. It explicitly distinguishes itself from list_research and from the analysis-creating siblings, so an agent can identify it without schema inspection.

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?

Tells the agent exactly when to use it: to reread a stored result obtained from list_research. It also names the alternatives (research_niche, research_account, analyze_reel) and the condition that selects them – running a new, paid analysis.

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