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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing the shape of the payload (price band, rate-card year, last verified date, media kit link), which tells the agent what evidence it will get back. It omits not-found/ambiguity handling, so it is not fully transparent.

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 opens with the core purpose, then enumerates fields, then closes with the lookup key. Dense but every clause carries information; the only weakness is that the long field enumeration slightly buries the parameter guidance at the tail.

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 and one undocumented parameter, the description correctly compensates by listing the returned fields and the lookup modes. What remains missing is failure behavior (unknown slug, multiple partial matches) and whether the media kit link is guaranteed present — minor gaps for a single-parameter read 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 0%, so the description must carry the parameter meaning, and it does: the single string accepts either a slug or a partial name. That partial-match capability is a genuine semantic addition an agent could not learn from the bare 'string' type. It does not specify matching rules or case sensitivity.

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+resource ('Public details for one publication') and enumerates the exact fields returned, which clearly separates it from list-style siblings like search_publications. It stops short of naming a sibling directly, but the singular scope 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?

'Look up by slug or (partial) name' implies this is the single-record retrieval path, so an agent can infer it should reach for this after finding a publication. However, it never says when to prefer this over search_publications or what happens if multiple publications match a partial name, leaving the routing decision partly to inference.

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