study_read_resource

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the safety bar is partially covered. The description adds real behavioral context beyond them: local-vs-remote execution, browser use, and the asynchronous job_id polling path that explains why this 'read' is not read-only. It stops short of describing content format or job lifecycle.

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?

Four short sentences, each front-loading a distinct behavior (default path, refresh, job_id, exclusions). Dense and largely waste-free, though 'Dates require source interpretation' is a cryptic aside that could be clearer.

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?

No output schema exists, so the description carries the return burden, and it does explain the two return modes (immediate content vs. job_id). However, it leaves item_id resolution, poll cadence, and the shape of returned content unspecified, which is a meaningful gap for a 2-param 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?

With 0% schema description coverage, the description must carry parameter meaning. It does clarify refresh=True (obtain current remote contents vs. default local fast path), but item_id is only obliquely described ('observed Learn page/file') and no format/identifier guidance is given.

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 ('Read an observed Learn page/file'), which is a clear scope. It does not explicitly differentiate itself from close siblings like study_read_file, study_read_service, or study_download_resource, so the agent must infer the boundary.

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 context for one mode: verified local files return immediately by default, and refresh=True fetches current remote contents. It also notes 'Does not submit forms' as an implicit exclusion, but it never names alternatives or says when to prefer a sibling reader/downloader instead.

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