tmz_author

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

With no annotations provided, the description carries the burden of explaining behavior. It discloses an important caveat: TMZ credits content to 'TMZ Staff' and has no journalist profile pages, so this endpoint surfaces the closest available per-person coverage hub. It could also describe response format or pagination, but for a simple read endpoint it is adequately 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?

The description is front-loaded with the main purpose, then explains what is returned and why this endpoint exists. Each sentence earns its place, and the explanation of TMZ's byline convention is valuable rather than padding.

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?

The description gives the essential input and output concepts: a person's profile hub with name and recent coverage, accessed via URL or slug. However, there is no output schema, and the description leaves response shape, pagination behavior, and the practical requirement to provide either url or slug mostly implicit.

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 schema already explains url, page, and slug clearly. The description reinforces that a canonical person-hub URL or slug is the input, but it does not add meaningful semantics beyond what the schema provides.

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 clearly states a specific verb and resource: 'Get a TMZ person profile' and describes the output as the person's name and most recent TMZ coverage. It also distinguishes this from typical journalist-author endpoints by explaining that TMZ uses a single 'TMZ Staff' byline and that this endpoint returns the per-person coverage hub.

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?

The description gives strong context for when this tool makes sense: when a TMZ person profile/coverage hub is needed, and specifically that no individual journalist profile pages exist. It does not name an explicit alternative tool, but the rationale makes the intended use case clear.

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