document_load

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

With no annotations provided, the description must fully convey behavioral traits. It only states the action without disclosing side effects, such as whether loading overwrites an existing session, requires authentication, or alters state. The agent is left guessing about the consequences.

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 a single sentence with no redundant information. It is front-loaded and efficient, containing only essential elements.

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 tool's foundational role for many sibling operations, the description is too sparse. It does not mention that the file is parsed and stored, that the session is available for other operations, or what happens on error. An agent lacks sufficient context to understand the full impact of this action.

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 coverage is 100%, so the schema already documents parameters. The description adds minimal value beyond echoing the purpose of 'session' and 'filePath'. It does not elaborate on the format parameter's auto-detection or provide additional context for usage.

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 verb 'Load' and the resource 'OpenAPI or AsyncAPI file into a named session'. It distinguishes itself from sibling tools by being the only tool that loads a file into a session, which is unique among the many document manipulation tools.

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 provides no guidance on when to use this tool versus alternatives like document_create or document_clone_session. It lacks any mention of prerequisites, preconditions, or scenarios where this tool should or should not be used.

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