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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool runs frameworks 'in parallel' and warns that it 'takes longer,' which is meaningful behavioral context beyond a generic 'analyzes content.' For a non-destructive analysis tool, this level of transparency is adequate, though it does not mention potential side effects like content storage or rate limits.

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 well-structured and front-loaded, with a clear verb-first opening, a bulleted list of frameworks, and a direct usage sentence. It is slightly redundant—'most thorough' and 'most comprehensive view' say the same thing—but every sentence otherwise earns its place.

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 complex tool that runs seven frameworks, the description adequately covers the scope, framework list, usage context, and performance trade-off. An output schema exists, so return-value documentation is not the description's burden. It does not explicitly reference sibling specialized tools, but the sibling list and framework names provide enough context for an agent to choose appropriately.

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 100%, so the baseline is 3. The description adds only marginal value by noting that Persuasion is 'domain-specific' and listing Platform and Quality as frameworks, which loosely maps to the domain and platform parameters but does not explain them beyond what the schema already states. No additional semantic guidance is needed.

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 clearly states a specific action ('Run all 7 COS frameworks in parallel') and identifies the exact resource and scope. It differentiates from sibling tools by explicitly positioning itself as 'the most thorough analysis option' and listing the included Core 4 and Extended 3 frameworks, which directly maps to the specialized sibling 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 description says when to use this tool: 'Use this when you need complete analysis across all dimensions.' It also provides a clear trade-off by noting it 'takes longer but provides the most comprehensive view.' It does not explicitly name sibling alternatives or state when not to use it, so it falls short of a 5.

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