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

Annotations already mark it read-only, open-world, idempotent, and non-destructive. The description adds meaningful behavioral context: anonymized self-clone-excluded data, available=false with a reason rather than low-sample estimates, draft proposals excluded, and historical-only descriptive output. This goes well beyond the annotations and contains no contradiction.

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 information-dense but well structured: a one-line summary, a clear payload definition, data-quality caveats, governance exclusions, and a workflow note. It front-loads the core purpose and every sentence contributes useful selection or invocation context.

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 read-only intelligence report with an output schema and strong annotations, the description covers what data is included, what is excluded, availability behavior, and the intended workflow before clone_strategy. The main gap is the undocumented input parameters, which is minor given they are all optional and the output schema exists.

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 input schema has 0% description coverage for limit, caller_id, and strategy_type. The description never mentions these parameters or how they affect the report, so it does not compensate for the schema gap. Their names are partially inferable, but no real semantic guidance is provided.

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+resource: get a clone-marketplace live performance and approvals report. It clearly identifies the content (performance deltas, approval trail) and distinguishes itself from cloning by referencing clone_strategy. The purpose is unmistakable even among many similar get_* siblings.

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 explicitly frames the tool as an INTELLIGENCE step before cloning one via clone_strategy, giving an actionable workflow. It does not enumerate exclusions or compare against other strategy-research siblings like get_strategy_leaderboard, but the primary when-to-use guidance is clear.

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