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

With no annotations provided, the description carries the transparency burden. It usefully discloses that only published case studies are returned, which is a non-obvious behavioral constraint beyond the tool name, and it clarifies that filtering is optional. It does not discuss ordering, pagination, or errors, but for a read-only list operation the key behavior is disclosed.

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 efficient sentence, front-loaded with the core purpose and followed by the filtering options. Every word contributes meaningful information with no redundancy.

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?

The description is adequate for a simple listing tool, but it lacks return-shape details and no output schema is provided to compensate. It also omits guidance on how this tool relates to search or when its optional filters should be supplied, leaving some context to inference.

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 clarifies that service_id and technology are optional filters, adding meaning beyond the raw schema. However, it does not explain limit or language semantics, though those are partially self-evident from their names and schema constraints.

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 identifies the action: list case studies, restricted to published ones only. It also states the optional filters (service or technology), which distinguishes it from broader sibling tools like search or single-entity getters such as get_company and get_service.

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 guidance is given about when to use this tool versus alternatives such as search or get_service. The optional filtering behavior is mentioned, but there is no when-to-use, when-not-to-use, or explicit contrast with sibling tools.

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