Read a PromptEye help article

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds critical behavioral context: it explicitly frames the content as documentation to relay, not instructions to the agent, and warns against improvising beyond the article. This prevents the agent from treating the article as authoritative for its own actions, which is a nuanced behavioral disclosure.

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 concise, with no filler, and front-loads the most important instruction (take the path from list_help_articles) early. It then clarifies the behavioral expectations in a clear, direct text block. Every sentence serves a purpose.

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 that the tool has one simple parameter and is read-only, the description is complete. It covers how to get the path, what to do with the content, and how to handle gaps in coverage. No additional information is needed for correct invocation.

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 single parameter 'path' is fully documented in the schema with a clear example, so schema coverage is 100%. The description reinforces that the path comes from list_help_articles and provides a concrete example, which adds useful context for the agent on how to obtain the correct value. This goes slightly beyond the schema's basic description.

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?

Clearly identifies the tool as reading a help article and returning its content in Markdown. It specifies the resource ('PromptEye help center') and the output format, and it is distinguishable from siblings like list_help_articles because it focuses on reading one article rather than listing them.

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?

Provides explicit instructions on how to use the tool: take the path from list_help_articles, answer from the article's content, and point the user to the help center if the article doesn't cover the question. It also advises to mention when the article is insufficient rather than improvising.

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