get_full_text

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

With no annotations, description carries full burden. It discloses large size, truncation behavior with truncated flag, required ID formats, and subset limitations. Does not mention rate limits or permissions but covers main operational traits.

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?

Concise with front-loaded purpose, warnings, parameter usage, and examples. No unnecessary sentences. Could be slightly more structured but effective.

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?

Given 4 parameters and existing output schema, description covers main behavior, limitations, and truncation. Lacks error handling details but overall sufficient for agent to use correctly.

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%, so description must add meaning. It explains 'id' and 'max_chars' well. 'id_type' is implied via examples but not explicitly described. 'encoding' is not explained. Partial coverage.

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?

Description clearly states it fetches the full text of a PMC Open Access article in BioC JSON format. Specific verb (fetch), resource (full text of PMC article), and format (BioC JSON). This distinguishes it from siblings like get_summaries which likely return abstracts.

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?

Description advises to use sparingly due to large size and notes availability only in certain subsets. Provides examples. However, lacks explicit comparison to siblings or guidance on when not to use.

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