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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds meaningful scope ('public active' only) and return type ('listing summaries'), but does not disclose pagination behavior, result ordering, or that no search-query parameter exists.

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 a single front-loaded sentence with no filler. It is efficient, though its extreme brevity leaves some useful context unstated.

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 read-only listing tool with rich safety annotations and no output schema, the description covers the basic purpose and scope. However, it leaves gaps around what a 'summary' contains, how pagination works, and the absence of a search-query parameter, which could confuse an agent expecting keyword search.

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% for limit and offset, so the description must compensate. It only uses the word 'page' without explaining what limit/offset control, their defaults, or their allowed ranges; an agent still lacks semantic detail beyond the parameter names.

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 names a specific verb ('Search or page') and resource ('public active Mahshar API listing summaries'), making it clear this is a discovery/list tool rather than a detail or execution tool. It implicitly distinguishes from siblings like get_api and execute_api_call by focusing on listing summaries, though it does not explicitly name them.

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?

Usage is only implied: 'Search or page' suggests browsing available APIs, but the description offers no explicit guidance on when to use this versus get_api (for details) or execute_api_call (to invoke). There are no exclusions or alternative routing instructions.

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