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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond them: 'Reads no private records and needs no connection' and 'one bounded page', though it does not describe return format or pagination behavior in detail.

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 front-loaded sentences with no wasted language. The core purpose and safety notes are stated efficiently.

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?

The description identifies what is discoverable and adds safety context, but for a query tool with a nested input object and no output schema, it does not explain the category filter, pagination semantics, or what a result page contains. It is adequate but leaves clear gaps.

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 0%, and the description does not explain the nested input fields limit, query, offset, or category. 'Search or browse one bounded page' gives only a vague hint about query and pagination, leaving most parameter semantics to inference.

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 uses a specific verb, 'Discover', and names a clear resource: IPP workspace capabilities, example prompts, training, and secure website handoffs. It is distinct from the invoice-operation siblings, though it does not explicitly differentiate itself from similarly named tools such as get_workspace or get_workspace_setup.

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 implies usage by saying 'Search or browse one bounded page', which suggests filtering and pagination, but it does not state when to use this tool versus alternatives such as get_workspace. No exclusions or prerequisites are given.

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