get_publication_text

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

No annotations are provided, so the description carries the burden of disclosure. It mentions a 'shared scope gate' as a behavior, but gives no detail on what happens if the gate is not passed, error conditions, permissions, or response format. The minimal context is insufficient for an unannotated tool.

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?

The description is only one sentence and concise in length, but it is under-specified rather than appropriately concise. It omits critical operational details, making the brevity a liability rather than a strength.

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?

With 3 parameters, no output schema, and no annotations, the description needs to provide more context but does not. It covers the basic purpose and a vague prerequisite but leaves the tool's usage, parameter semantics, and expected results unexplained, making it incomplete for an AI agent.

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% and the description does not describe any parameter (url, question, section_keyword). The agent receives no guidance on what each parameter means or how to fill them, leaving the schema's bare names and types as the only information.

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 clearly states the tool fetches 'narrative publication text,' which is specific and distinguishes it from siblings like get_publication_overview (overview) and get_data_file (data file). However, it lacks explicit mention of how it differs from search_publication or check_query_scope.

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 phrase 'after passing the shared scope gate' implies a prerequisite step (likely using check_query_scope first) but does not explicitly name the gate or state when to use this tool versus alternatives. Usage guidance is implied rather than clearly stated.

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