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

Annotations already cover safety (readOnly, idempotent, non-destructive, open world), so the description earns credit by adding the section-fallback lookup behavior, the fact that only metadata plus a short excerpt come back, and the citation obligation with the returned URL. Those are real behavioral traits not expressed in the annotations or schema.

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?

Three tight sentences, front-loaded with the resource and identifier, then lookup behavior, then the return-shape and citation constraint. No sentence is redundant with another.

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 output schema, the description carries the return-value burden and does it — metadata plus a short excerpt, full text only on-site. Missing only edge-case behavior such as what happens when no section matches, which matters for an open-world lookup 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?

Schema coverage is 100% and the section enum already documents the default and fallback, so the description largely restates structured data. It adds the useful framing that a wrong section guess is non-fatal, but no slug format or matching guidance beyond the schema example.

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?

States a specific verb and resource — 'Fetch a CloudJobs insight post by slug' — which clearly separates it from search_insights (search) and the other get_* tools (company, job, salary). It stops short of naming the sibling it complements, so an agent must infer that search_insights is the discovery counterpart.

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?

Implies usage: you need a known slug, and the section fallback behavior tells the agent it need not pick a section precisely. There is no explicit when-not or a named alternative such as search_insights for the case where the caller has only a topic, not a slug.

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