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

With annotations already covering read-only, idempotent, and non-destructive behavior, the description adds useful context: default returns 3-5 ranked images per project, limitProjects caps projects at three, and unanchored requests return clarification. It does not disclose auth or rate limits, but the added behavioral traits are substantive.

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 tightly written sentences with zero waste. The primary return behavior is front-loaded, followed by the edge-case clarification behavior, making it easy to scan.

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?

An output schema and safety annotations reduce the burden, so return values and safety profile need not be explained. However, with six parameters and 0% schema description coverage, the description is incomplete for parameter semantics and does not fully help an agent understand all inputs.

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 six parameters, so the description must compensate. It only implicitly clarifies limitProjects (up to three) and imagesPerProject (3-5 images); it says nothing about query, aiFilter, category, or projectSlug, leaving most parameters undocumented.

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 states a specific verb ('Returns') and resource ('thumbnail plus 3-5 ranked artwork images') scoped to a project or category. It clearly distinguishes default behavior from the limitProjects variant, though it does not explicitly contrast with sibling tools like get_project_by_slug or list_portfolio_projects.

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 gives clear usage context: use for a named project or category; unanchored requests yield a clarification rather than an arbitrary project. This provides a when-to-use and a when-not condition, but it does not name alternative tools for cases like listing all projects or fetching project metadata.

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