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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds freshness context ('Current') and the public-section restriction, but says nothing about result volume, ordering, or staleness, and return shape is covered by the output 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?

A single tight sentence with the resource, freshness, scope, and input constraint all front-loaded; no filler.

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 annotations and an output schema, the description covers purpose, scope, and input provenance. Only minor gaps remain (ordering, volume expectations).

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 lists canonical slugs, so the schema does the heavy lifting. The description adds provenance semantics the schema lacks – valid values must be sourced from nymag_sections – which meaningfully reduces invalid-input risk.

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 ('Current New York Magazine headlines') with an explicit scope ('one public section'), which separates it from siblings like nymag_article and nymag_news without opening a schema.

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?

Tells the agent where valid inputs come from ('section must come from nymag_sections'), which is effectively a prerequisite workflow step. It stops short of naming when-not to use this tool or explicitly contrasting with nymag_news.

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