get_document_text

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

No annotations are present, so the description must carry the burden. It discloses that the tool returns full plain text and requires a prior get_document call to obtain the URL. However, it does not discuss error handling, output format beyond 'plain text', or any side effects. This is adequate but not rich, so a 3.

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 sentences, zero redundancy, front-loaded with the primary action. Excellent.

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 single-parameter fetch tool, the description covers the essential workflow: what it does and how to get the input. It doesn't need to explain return values since there is no output schema, but it could mention error cases. Complete enough for the tool's simplicity.

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 covers 100% with a clear description, giving a baseline of 3. The description adds the workflow context of obtaining the URL from get_document, which provides additional semantic value. Thus a 4.

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?

The description uses the specific verb 'Fetch' with the resource 'full plain text content of a Federal Register document', clearly distinguishing it from sibling tools like get_document which provides metadata. It also includes the prerequisite step, reinforcing its specific role.

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 explicitly instructs to 'First use get_document to get the raw_text_url, then pass it here', providing clear when-to-use context. It doesn't explicitly state exclusions or alternative tools, so it's a 4 rather than 5.

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