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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real semantics on top: the returned query is described as 'safe' (implying redaction), and it explicitly warns that a retained active subscription only proves registration, not that a client received or acted on a camera event. That caveat prevents a concrete misreading of the result and is not derivable from any structured field.

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 sentences, front-loaded with the action and resource, followed by the return contents and the one critical caveat. Nothing is redundant with the name or title.

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?

A one-parameter read tool with full schema coverage, explicit annotations and an output schema, so return values need not be spelled out further. The description nonetheless names what comes back and closes the main interpretive risk, leaving nothing an agent needs missing.

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% and the single id parameter is documented in detail, including the 'never use a display name or endpoint ID' constraint. The description's 'exact ID returned by subscription_list' largely restates the schema, so it adds little beyond 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 (Inspect) and a precisely scoped resource (one Port OS event subscription, by exact ID), and names the sibling that produces that ID. An agent can separate it from subscription_list, subscription_cancel and subscription_label_edit without opening a schema.

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 tells the agent where the required ID comes from (subscription_list) and the schema forbids substituting a display name or endpoint ID, which rules out the main misuse. It does not contrast this tool with read-adjacent siblings such as endpoint_show, but the lookup path is unambiguous.

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