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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. The description adds real value beyond them: the output is Markdown matching the .md rendition, and the scope is limited to public content with no signed-in app access.

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 tight sentences: the first delivers purpose, format, input forms, and examples; the second delivers the access boundary. Nothing is wasted and the key scoping constraint is front-loaded.

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?

An output schema exists, so return values need no explanation, and the description covers input forms and access scope. Only minor gaps remain, such as behavior on an invalid or non-existent path.

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 description coverage is 100% and the single 'path' parameter is fully documented in the schema, including pattern, length limits, and accepted forms. The description's examples ('/pricing', '/facts', '/docs/faq') largely restate what the schema already conveys, so this is baseline territory.

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?

States a specific verb (Read), resource (one public Genko Prior Auth page), and output format (Markdown, same as its .md version), with concrete path examples. An agent can distinguish this generic page reader from more targeted siblings like get_pricing and get_product_facts.

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?

Explicitly scopes usage with 'Public pages only; the signed-in app is never available,' which tells the agent when this tool applies. However, it does not name an alternative such as search_docs for when the agent does not already know a path or URL.

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