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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's added value is limited to what the payload contains (key points, FAQ, full-post link), which is useful but modest given no output schema. It says nothing about failure behavior for invalid slugs or whether results are cached.

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, no filler, and the resource identity plus return contents are front-loaded before the identifier source. Every clause earns its place.

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 one-parameter read tool with no output schema, the description carries the return-value burden and does so by naming key points, FAQ, and the full-post link. The main remaining gap is what happens when the slug is unknown or invalid, but that is minor for a simple lookup.

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 100% and the single slug parameter is documented in the schema with format examples. The description echoes the same slug/URL duality and adds only the provenance hint that the slug comes from search_guides. Baseline 3 is appropriate where the schema does the heavy lifting.

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 resource (one OnPress guide) and enumerates what it returns: key points, FAQ, and the link to the full post. It also names the sibling search_guides as the source of the identifier, which separates discovery from single-item retrieval. It stops short of an explicit 'fetch one guide' verb phrasing, but the purpose is unambiguous.

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?

"by the slug or URL from search_guides" establishes the workflow: call search_guides first, then use this tool on a chosen result. It gives clear context for when to use it, though it does not state exclusions (e.g., that it cannot list or search, and that search_guides must be used for discovery).

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