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

Annotations already mark it as a read-only, non-open-world operation, and the description adds useful behavior beyond that: content is returned as markdown and long pages are truncated. It does not explain truncation limits or pagination, but the key behavioral caveat is disclosed.

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 three compact sentences with no wasted wording. The core purpose is front-loaded, followed by accepted input forms and the truncation caveat.

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?

For a simple one-parameter read tool with annotations and no output schema, the description is nearly complete: it covers source, format, accepted inputs, and truncation. It could be slightly stronger by explaining what happens when a page is cut short, but no critical invocation detail is missing.

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 path parameter is already well documented. The description adds minor clarity by mentioning docs.elfhosted.com links and the relationship to search_docs results, but it does not add substantial syntax or format detail beyond the schema.

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 states a specific verb and resource: read one page of the public ElfHosted docs as markdown. It also distinguishes the tool from search_docs by explaining that search_docs returns paths that get_doc can consume.

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?

It gives clear usage context: provide a page path like "app/plex" or "trial", or a docs.elfhosted.com link as returned by search_docs. It does not explicitly state when not to use it versus siblings such as browse_apps, but the intended use is clear.

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