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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so safety is covered elsewhere. The description adds real behavioral facts — default filter is REAL and results are capped at 100 — but says nothing about pagination, ordering, or cost, and its 'requires testId and/or operationId' precondition contradicts the schema's zero required parameters.

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, each carrying distinct information (resource, precondition, defaults/caps), with the core purpose front-loaded. No filler.

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 10-parameter read tool with 20% schema coverage and no output schema, the description accounts for only a few parameters. Key filters such as executionId, interactionId, includePayloads, and retryCount are undocumented anywhere, and the stated precondition is inconsistent with the schema.

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 only 20% across 10 parameters, so the description carries heavy burden. It clarifies testId/operationId, the interactionType default of REAL, and the 100 cap on limit, but leaves executionId, interactionId, retryCount, includePayloads, and botId entirely unexplained.

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 ('List recorded API operation interactions'), which is clear on its own. It does not distinguish itself from the nearest sibling, get-api-operations, which an agent would plausibly confuse it with.

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?

'Requires testId and/or operationId' is the closest thing to a usage rule, giving the agent a precondition for calling. It names no alternatives and no when-not-to-use case, and the 'requires' claim conflicts with the schema where required parameters = 0.

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