charlotte_reload

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

The description discloses the main behavior (reload) and output (page representation). With no annotations, it carries the full burden but does not mention potential side effects (e.g., losing unsaved form data) or clarify if it's a forced reload from server.

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 concise sentences with no wasted words. The description is front-loaded with the key action and immediately provides the outcome.

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 simplicity of the tool (reload page), the description covers the essential purpose and result. There is no output schema, but the mention of 'page representation' is adequate for basic understanding.

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%, and the schema already describes both parameters ('hard' and 'detail') well. The description does not add further meaning or context beyond what the schema provides.

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 'Reload' and the resource 'current page', and specifies the outcome 'Returns page representation after reload'. This distinguishes it from sibling tools like navigate, back, forward, etc.

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 guidance on when to use vs alternatives (e.g., navigate or forward). The usage is implied as refreshing the page, but without mention of when not to use or how it differs from other navigation tools.

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