Read the EasyDeploy playbook

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

Annotations already declare readOnly/idempotent/openWorld=false, so the safety profile is covered. The description adds genuinely new behavior: the content 'ships with the server and changes between releases' (so results are version-dependent) and that it 'makes no API call', which explains why it always succeeds.

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?

The purpose is front-loaded and readable, but the parenthetical enumeration of the seven section names duplicates the enum already in the schema, and the return-shape sentence partially overlaps the output schema. Roughly one clause could be cut without loss.

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?

An output schema exists, so return values need not be explained, yet the description still notes the guide_version and next-section fields. Combined with purpose, usage context, parameter behavior and versioning caveat, an agent has everything needed to call it correctly.

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%, so the description must carry the load. It explains that 'section' selects one part or 'all', names the default ('overview'), and describes what each selected value returns. The parenthetical list essentially restates the enum, but the default and the 'all' behavior are real additions.

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 EasyDeploy data-science playbook' — and enumerates what the playbook covers (prepare, split, upload, train, validate, predict). No sibling tool returns guidance content, so the agent can distinguish it immediately from the operational tools.

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?

Gives a clear use context: 'Useful at the start of a modeling task.' It does not name an alternative, but none of the siblings overlaps (they are all operational read/write endpoints), so no exclusion is needed. Slightly short of explicit when/when-not framing.

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