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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real context beyond them: no auth required, that oversized responses return a field directory rather than the data, and that the tool has no generate/email side effects. It stops short of describing what a typical report payload looks like.

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 short sentences, front-loaded with the core capability, then the large-response mechanism, then the boundary. Nothing is repeated from the title or schema and no sentence is 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 seven-parameter read tool with no output schema, the description covers the two things an agent most needs: auth-free access and the field-directory/path indirection for large payloads. The remaining gap is what a report actually contains and whether limit/offset apply uniformly across all fifteen report types.

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 57%, so several parameters (limit, offset, report enum values) carry no inline description. The description compensates by explaining the paging model ('select a path and page arrays'), which is what path/limit/offset/before jointly implement, and by stating the count of fifteen reports behind the enum.

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 concrete verb and resource ('Read one of fifteen published market reports') and bounds it with an explicit non-capability ('Never generates or emails a report'). It's clear what it does, though it doesn't explicitly contrast with near-neighbors like read_archive or read_workspace, leaving the agent to infer which read tool fits.

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?

Gives useful operational guidance ('without signing in', 'select a path and page arrays') and one exclusion (no generation or emailing). It never says when to pick this over read_archive or read_workspace, so routing among the read_* siblings remains inferred.

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