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

With no annotations present, the description carries the full burden and does well: it discloses that the effect is scoped to scheduling rather than deletion ("Existing posts remain in the library"), that it is reversible via resume_stream, and that own_profile streams are rejected. It does not mention permission/auth requirements or what the call returns on success, which keeps it below a 5.

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?

Three short sentences, front-loaded with the effect, then the data-retention reassurance, then the alternative and the exclusion. Nothing is redundant and nothing could be cut without losing an operational fact.

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 single-parameter state-change tool with no annotations and no output schema, the description covers effect, data safety, reversibility, and a failure precondition. Only auth requirements and confirmation of return state are absent, which is a minor gap at this complexity.

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?

Only one parameter and schema description coverage is 100%, with the schema already telling the agent to take the ID from list_streams. The description adds no further semantics about stream_id, so the baseline 3 applies.

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 ("Pause a stream") plus the precise mechanism it affects ("stops running on its cron schedule"). This cleanly separates it from delete_stream, run_stream_now, and resume_stream in the sibling list.

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?

Gives an explicit alternative ("Use resume_stream to re-enable it") and an explicit exclusion ("own_profile streams are billing-managed and cannot be paused here"). An agent knows both the reverse operation and the case where this call will fail.

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