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

The readOnlyHint annotation already communicates that this is a safe, non-mutating operation. The description adds scope and content context but does not describe response format or any other behavioral details. Since there is no output schema, a bit more about what the agent should expect as a return value would strengthen transparency.

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 description is compact and well-ordered: it states the core function first, adds usage timing second, and finishes with a tidy topic list. No filler or redundant restatement of the schema.

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 single-parameter, read-only guide-fetching tool, the description covers what the tool does, when to use it, and all valid topics. The main gap is the lack of an explicit output format, but the term 'guide' and the listed content categories make the outcome reasonably predictable.

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 coverage is 100%, so the baseline is 3. The description adds value by enumerating the valid topics and enriching the 'workflow' option with '(the full build order)', clarifying the guide's content categories beyond the schema's terse 'Which guide to fetch'.

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 and resource: 'Get the full canonical guide' and explains what the guide contains (rules, schemas, plan limits, embed contracts). It clearly distinguishes this from sibling getters like get_project or get_form by framing it as a meta-guide for how Dplooy features work.

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 description explicitly states when to use the tool: 'Call this BEFORE using a feature for the first time.' It does not discuss exclusions or alternative tools, but no sibling appears to offer the same guide functionality, so the when-to-use guidance is sufficient.

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