read_content

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is partly covered; idempotentHint=false is not explained. The description adds real value beyond the annotations with the security caveat that fetched content is untrusted material and must not be treated as executable instructions, a meaningful prompt-injection warning for an open-world reader.

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?

Two short, front-loaded sentences with no filler; the primary usage path is stated first. The terseness verges on under-specification, but nothing in the text is redundant.

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 covers the two input paths and the trust caveat, but with no output schema it does not say what the read returns, how refresh affects retrieval, or how the platform enum constrains url handling. Adequate but with clear gaps for a 4-parameter open-world reader.

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 0% across 4 parameters, so the description must carry the semantics. It clarifies content_ref (comes from search results) and that url must be a full url paired with platform, but it says nothing about the refresh flag, nor whether url is usable without platform or content_ref.

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 ('阅读'/read) and the exact resource it consumes: the content_ref carried by search results, or a platform + full url pair. That is enough to separate it from siblings like search and read_comments, though it never names those siblings explicitly to sharpen 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?

The description implies the workflow: after a search, pass the content_ref; alternatively supply platform plus a complete url. It does not state when to prefer content_ref over url, whether both may be combined, or when to use read_comments instead.

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