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

Beyond the read-only and idempotent annotations, the description adds substantive behavioral context: pending is not success, failed can indicate an uncertain write, and the tool deliberately does not expose saved arguments, narrative results, or cross-connection requests. These are meaningful operational and privacy traits that an agent could not infer from structured fields alone.

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 purpose, followed by status-interpretation caveats and exposure boundaries. Each sentence adds distinct value and there is no redundant or filler language.

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 one-parameter status-check tool with no output schema, the description covers important behavioral warnings and privacy boundaries, but it omits the meaning of the required 'id' parameter and does not describe what a successful return looks like. It is adequate but incomplete for correct invocation.

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?

The sole parameter 'id' has zero schema description coverage and the description never clarifies whether it refers to an action ID, approval ID, or something else. With low schema coverage, the description should compensate by explaining the identifier, but it does not.

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 uses a specific verb ('Check') and names the resource precisely: this connection's saved action or approval outcome. It clearly scopes to the current connection and excludes another connection's requests, though it does not explicitly name sibling tools as alternatives.

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 phrase 'Check this connection's saved action or approval outcome' implies when the tool is useful, but there is no explicit guidance on when to prefer it over siblings like review_record or fetch. The note that pending/failed statuses need careful interpretation adds useful context but does not constitute alternative-selection guidance.

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