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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description only restates the negative boundary and the argument-matching requirement; it says nothing about error handling for an unknown operation name or how the fetched schema is validated.

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 action, then the prerequisite, then the exclusion. Every clause carries information and nothing is padded.

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 an output schema present, return values need no explanation, and the dynamic-dispatch nature of the tool is addressed by pointing at find_operations and the fetched schema. The definition is nearly complete for a generic dispatcher, though it omits failure behavior for invalid operations.

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 0% and the 'arguments' parameter is a free-form object, so the schema alone cannot tell an agent how to populate it. The description supplies the missing semantics: 'operation' is a name obtained from find_operations and 'arguments' must conform to the schema fetched for that operation. This is meaningful compensation for the coverage gap.

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 states a specific action (execute an advanced read), its provenance (an operation discovered with find_operations), and its boundary ('Cannot edit or launch'), which separates it from edit_draft_advanced and launch_test. It stops short of explaining what family of resources these reads cover, so it is clear rather than exhaustive.

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?

It gives an explicit prerequisite chain - first find_operations to discover the operation, then pass arguments matching the fetched schema - plus an explicit when-not ('cannot edit or launch'). No named alternative for the read case itself, but the workflow context is unambiguous.

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