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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses filter behavior, empty-list result for unknown values, the ownership/builtBy fields, and the special case of Frontend Mentor Lab counting as one entry. This is exceptionally transparent for a list operation.

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 four sentences and front-loads the core purpose. The caveat about Frontend Mentor Lab is important and not redundant. It is structured logically and avoids unnecessary verbosity.

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?

Given the lack of an output schema, the description covers essential return structure (ownership, builtBy) and behavioral nuances (filtering, case sensitivity, special case). It omits details like sorting or pagination, but these are likely not critical for a 17-item list.

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%, so the description must compensate. It explains the 'tag' parameter well (Title Case, case-insensitive) and the AND combination logic, but does not elaborate on the 'lens' parameter beyond the enum values. Partial compensation only.

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 clearly states a specific verb ('List') and a specific resource ('canonical portfolio case studies') with an explicit count (17 entries). It differentiates from siblings like 'get_project' (single project retrieval) by implying a collection operation.

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 explains when to use filters and how they behave (AND combination, case-insensitive matching), and notes that unknown values yield an empty list. It does not explicitly mention alternatives like 'get_project', but the context makes the usage clear.

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