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

With no annotations, the description carries the full burden. 'Get' implies a read-only operation, but it does not disclose pagination, filtering, sorting, or any side effects. The description is too terse to inform an agent about the tool's behavior.

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 only one sentence and essentially restates the title 'Get Prompts'. It is under-specified rather than concisely informative, providing no detail that would help an agent select or invoke the tool.

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?

Despite having 13 parameters, 4 required, no annotations, and no output schema, the description provides almost no context. It fails to explain what the response looks like, how pagination works, or what the required date range means. This is completely inadequate for a tool of this complexity.

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?

The schema has 13 parameters with 0% description coverage, yet the description adds no meaning to any of them. It never mentions page, pageSize, startAt, endAt, or any filter parameters, leaving the agent entirely dependent on the bare 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?

The description 'Get prompts list' clearly states the verb and resource: it retrieves a list of prompts. However, it does not differentiate from sibling tools like batch_get_prompt_by_ids or clarify the scope of the list (e.g., all prompts vs filtered).

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention the required parameters (page, pageSize, startAt, endAt) or any intended use cases.

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