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

Annotations already cover safety (readOnly, non-destructive, closed-world), and the description still adds real behavioral context: the response 'grows with workspace size' (a scale/perf warning), hidden flows appear only in the operations list and never in flows, and the blockFallback* fields are explained as application-level defaults for failed ACTION blocks with a pointer to get_action_schema.actionFailure. These are non-obvious data semantics an agent could not infer from the schema.

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?

Front-loaded with the purpose and the routing alternative, then details. The final sentence on blockFallbackStrategy is dense and slightly tangential to a 'get context' call, though it does explain fields the caller will receive, so it earns most of its space.

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?

No output schema exists, so the description carries the return-value burden and does: it lists the response sections, flags the one structural gotcha (operations vs flows), and explains the meaning of a cluster of fields. Combined with full parameter docs, an agent has everything needed to call and interpret it.

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 single applicationId parameter is fully documented in the schema, including the app_ vs usr_ key defaulting rule and the MCP_APPLICATION_REQUIRED failure mode. The description adds nothing about it, but with 100% schema coverage the baseline of 3 is appropriate.

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 ('Return the full application-level automation context') and enumerates exactly what that bundle contains: flows with folders, bots, variables, sequences, operations. It also positions itself against siblings by naming get_workspace_summary and describing the operations list as the home of hidden flow graphs.

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?

Explicitly frames itself as 'the broad orientation call' and states the alternative with its triggering condition: prefer get_workspace_summary when you only need names and counts. That is a clean when-to-use / when-to-use-something-else pairing rather than an implied one.

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