Get a Magic Lane documentation page

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description still adds real behavior beyond them: a 24000-character default return cap, a notice of remaining characters, and the offset mechanism for continuing — though it says nothing about auth, rate limits, or error behavior on non-Magic Lane URLs.

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?

Four sentences, front-loaded with the action and input forms, then discovery guidance, then the URL restriction, then pagination. Every sentence carries a distinct instruction with no filler.

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?

There is no output schema, so the description must explain what comes back; it does so (markdown content, truncation notice, offset paging). Combined with full schema coverage and annotations, an agent has everything needed to call it correctly.

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 baseline is 3. The description goes slightly further by giving concrete URL and /docs/... path examples for `url` and by explaining the offset/chunk relationship for paging, though maxChars is essentially restated from 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?

States a specific verb and resource ('Fetch the markdown content of a specific Magic Lane documentation page') plus the two accepted identifier forms, which cleanly separates it from search_docs, list_docs, and the batch sibling read_docs_batch.

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 routes discovery to 'search_docs or list_docs first' and states a hard exclusion: only developer.magiclane.com URLs, never other map providers' docs. That is a when-to-use plus a when-not-to-use rule in one place.

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