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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the useful constraint that results are scoped to the authenticated PromptUI user, but says nothing about ordering, pagination behavior, or what a queue item contains.

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?

A single front-loaded sentence with zero filler or repetition. It is arguably too terse for the information an agent needs, but nothing in it is wasted.

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 no-required-parameter read-only list with a fully documented schema, rich annotations, and no output schema to explain, the description covers what is needed to invoke it correctly. The remaining gaps (ordering, default sort) are minor for this tool class.

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 100% with defaults and enumerated valid values documented per parameter, so the schema does the heavy lifting. The description adds no meaning beyond it, which is the expected baseline when coverage is complete.

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 ("List GTM queue items") and scopes it to the authenticated user, so the agent knows it is a read over the user's own content. It does not differentiate from siblings like gtm_publish_content or gtm_generate_content, and "queue items" is not obviously the same resource as the title's "marketing content".

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?

No statement of when to call this versus alternatives (e.g. fetch a single item, generate, or publish), and no prerequisites beyond an implicit need to be authenticated. The agent must infer usage entirely from the name and schema filters.

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