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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'check if content meets' but doesn't explain what happens when limits are or aren't met (e.g., returns boolean, errors), whether it considers platform-specific rules beyond the named limits, or if there are side effects. This is a significant transparency gap for a validation tool.

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 a single, front-loaded sentence with no fluff. It uses a direct verb and clearly states the tool's purpose, achieving maximum conciseness without sacrificing clarity.

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?

Given the absence of an output schema and annotations, the description is incomplete. It doesn't specify what the validation returns (e.g., boolean, detailed report), what 'meets' means, or how limits are determined. It also fails to mention the contentType parameter's nuance (relevant only for YouTube), which the schema notes. A validation tool needs more explicit return/behavior details.

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%, so the baseline is 3. The description adds a small bit of context by mentioning 'for each social media platform,' implying the platform parameter determines which limits apply. However, it doesn't elaborate on how text, platform, or contentType interact, and the schema already describes these properties. The description adds marginal value.

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 the tool validates content against before-fold character and line limits for each social media platform. The verb 'check' is specific, and the resource (content before-fold limits) is precisely identified. It distinguishes itself from sibling tools like get-text-before-fold, which likely retrieves the before-fold text, by focusing on validation.

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?

Usage is implied by the verb 'check' – use this tool when validating content against before-fold limits. However, there is no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites (e.g., needing to fetch limits first). The description provides minimal contextual framing, but it's not misleading.

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