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

The description goes well beyond the annotations: it discloses hard limits (20 pages, 1000 records, 16 MiB), states that partial scans are discarded, and warns that contributed fields are unverified and must not be trusted for instructions. It also clarifies that structured fields are not an injection boundary, which is important behavioral and security context.

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 compact and front-loaded with the core purpose, then adds limits and security warnings in a logical order. Every sentence contributes distinct information and none restates the schema or annotations.

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 the single well-constrained parameter, the readOnly/openWorld/non-destructive annotations, and the presence of an output schema, the description covers all essential invocation and safety context. It explains bounds and untrusted-data handling, so an agent can call the tool without external knowledge.

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 schema provides page_budget with default/min/max but no description, and the tool description does not explicitly define the parameter. However, the phrase 'Bounded to 20 pages' plus the parameter name makes its purpose inferable, and 'Partial scans are discarded' adds consequence context.

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 opens with a specific verb and resource: 'Load one complete publication snapshot,' which clearly explains what the tool does. It does not, however, explicitly distinguish itself from the sibling haidaa_search_public_graph, so the agent must infer the difference from the name and 'complete snapshot' phrasing.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The phrasing implies this is for fetching a bounded full snapshot rather than searching, but the relationship to haidaa_search_public_graph is left implicit.

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