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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by indicating each guide contains a short answer plus a link, implying a lightweight advisory payload rather than full documents. It does not say how many guides are returned or in what order.

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?

It is a single sentence with no filler, but the bulk of it is a topic enumeration that reads like marketing copy rather than a front-loaded statement of what the tool returns. A leading clause such as 'Returns the available guides' would have made the purpose immediate.

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 no parameters and no output schema, the description carries the burden of explaining the return shape, and it does partially by noting each guide has a short answer and a link. It still leaves the agent guessing whether this returns a list of all guides, their titles, or full content, which matters for a discovery tool.

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 beyond what the empty schema shows. Baseline 4 applies for a no-parameter tool.

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 identifies the resource precisely — Alpha Flow Tech's guides on website/app costs, AI copying, stock/Sage systems, and software integration — which clearly separates it from siblings like estimate, get_item, and search_catalog. It never states the action verb explicitly (e.g., 'lists' or 'returns'), relying on the name list_guides to supply that.

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?

There is no when-to-use guidance and no mention of alternatives or exclusions. An agent must infer that this tool is for surfacing advisory articles rather than pricing, catalog, or ordering operations, which the sibling list shows are separate tools.

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