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

Annotations already declare readOnly, idempotent and closed-world, so safety is covered. The description adds real value beyond that by stating the return payload is full markdown identical to fetch, which tells the agent not to chain calls for the raw text. It does not disclose failure behavior for malformed slugs or truncated pages, which keeps it below 5.

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?

Three short sentences: what it fetches, when to use it, what it returns. Front-loaded with the action and scope, and every sentence carries distinct information with no repetition of the schema.

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?

With annotations covering side effects, a 100%-covered single parameter, an output schema handling return values, and a clear usage trigger, the definition is essentially complete. The only residual ambiguity is why one would choose this over fetch given the identical payload, which is left for the agent to resolve.

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?

There is one parameter at 100% schema description coverage, and the schema example ('enterprise/sso') mirrors what the description shows. The description reinforces dual URL-or-slug acceptance but adds no format rules, normalization behavior, or validation notes beyond the schema, so the baseline 3 applies.

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 a Mintive documentation page') and immediately constrains scope to public docs URLs or slugs, with two concrete examples. An agent can tell this is the docs-page reader rather than a generic web fetcher or a search tool.

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?

Gives a clear trigger ('when a user pastes a docs link or names a page directly'), which routes the agent well. It stops short of an explicit exclusion — e.g. 'use search when the user describes a topic rather than naming a page' — so the boundary with search and list_docs remains inferred.

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