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

With no annotations, the description carries the burden and does add behavioral context: the return is markdown raw text and no key is required (免 key), telling the agent this is an open, read-only content fetch. It omits caching/volatility and any size or freshness caveats, but for a zero-parameter read-only document fetch that is minor.

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 compact line that front-loads the resource, then the output format, then the must-read guidance and the auth note. Every clause carries information; nothing 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?

For a parameterless, annotation-free, no-output-schema tool, the description covers what it returns (markdown), why to call it (pre-integration reading) and the auth posture (no key). Only marginal items such as document stability or language locale are unaddressed.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter hints are present.

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 resource (tpool platform code of conduct) and the delivered form (markdown raw text), which is clearly distinguishable from the sibling search/quota/job tools. It does not explicitly contrast itself with any sibling, but the verb+resource pairing is unambiguous.

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 an explicit condition for when to call it (before onboarding/integration), which is more than implied usage. It stops short of naming alternatives or when-not-to-call, so it falls just under full guidance.

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