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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and mutability are fully covered by structured data. The description adds almost nothing beyond that, save for the hint that the response includes examples; it says nothing about output format, length, or versioning of the syntax documentation.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient but borders on under-specification rather than demonstrating tight structure over meaningful content.

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 zero-parameter, read-only documentation fetch, the definition is minimally sufficient: an agent knows what it gets and that it is safe to call. However, with no output schema present, the description should say what form the documentation arrives in (markdown text, JSON examples, size) and whether it covers the full language or a subset.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter information is missing because none exists.

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 names a specific verb ('Get') and resource ('FlowZap Code syntax documentation and examples'), making it clearly a reference-retrieval tool. It is implicitly distinguishable from siblings like flowzap_validate or flowzap_apply_change, but it never explicitly states that distinction.

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?

Usage is only implied: an agent can infer this is the reference to consult before authoring or validating FlowZap code. There is no explicit when-to-use statement, no mention of prerequisites, and no naming of alternatives such as flowzap_validate or flowzap_fix.

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