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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description does not need to restate it. What the description does add is the filtering semantics — published status and the strict "only linked to approved tools" constraint, which materially changes what comes back. It omits pagination behavior, default result count, and ordering, which are the remaining behavioral unknowns for a list endpoint.

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?

One sentence with the scope constraints front-loaded and no filler. It is efficient, though the brevity edges toward under-specification given the undocumented parameters.

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?

This is a simple, read-only, annotated list tool with no output schema and no required parameters, so the bar is modest. Still, for a paginated endpoint the description should say what the default page size is and whether locale affects filtering or output language; without that, an agent can call it but cannot predict the result set's shape.

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?

All three parameters (limit, offset, locale) have 0% schema description coverage, so the description carries the full burden — and it says nothing about any of them. An agent gets no guidance on the default page size, whether limit is capped at 50 in practice, or what locale actually does (fall back? filter? translate?). The enum and min/max constraints in the schema hint at shape but not meaning.

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 and resource ("List guides") and adds two concrete scope qualifiers: only published guides, and only those linked exclusively to approved tools. That is enough to tell it apart from get_guide, which fetches a single guide. It stops short of an explicit sibling contrast, so it lands at 4 rather than 5.

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 by the word "List"; the agent must infer this is the browse/enumerate entry point and that get_guide is the single-item alternative. There is no statement of when-not to use it, and no mention of how it relates to compare_tools or search_tools for discovery.

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