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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Does NOT publish or modify content'. It also explains the non-idempotent behavior implicitly by tying evaluation to the 'live news cycle', which accounts for varying results across calls. It stops short of describing latency, cost, or how the score is derived.

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 tight sentences: the first states the action and domain, the second lists return values and the non-mutating constraint. Nothing is wasted and the core purpose 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?

With no output schema, the description carries the return-value burden and does so by naming the four outputs. For a two-parameter read-only tool this is nearly complete, though it could clarify what a 'timeliness verdict' contains or how the rewrite differs from the input.

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 both parameters (post_content and the platform enum with its default) are already fully documented in the schema. The description adds no format, length, or platform-specific guidance beyond that baseline.

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 and resource ('Evaluate a draft social post') plus the domain ('live music industry news cycle'), and enumerates the outputs (feedback, 0-100 score, timeliness verdict, rewrite). This clearly separates it from generate_post and schedule_post 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 negative guidance 'Does NOT publish or modify content' usefully rules out write intent, but the description never names an alternative or states when to prefer this over generate_post or generate_post_dry_run. Usage is implied rather than directed.

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