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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so safety is covered. The description adds genuinely new behavioral facts not in annotations or schema: results are scoped to the signed-in user and returned newest-first. It omits pagination behavior beyond the limit parameter, which is the main remaining gap.

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 sentence with zero waste, front-loading the action and scope, with the ordering detail appended where it belongs.

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, annotation-backed read tool with one documented parameter and no output schema, the description covers who/what/ordering. Slightly short of full completeness because it says nothing about the shape of returned project entries or paging beyond limit.

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% and the single limit parameter is fully documented in the schema (max 100, default 25). The description adds no parameter semantics beyond that, so the baseline 3 applies.

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+resource (list ... projects) plus scope (signed-in user's Kulture campaign projects) and ordering (newest first), which is enough to distinguish it from create_project in the sibling list. It does not explicitly contrast with other list_* siblings, but those cover different resources.

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?

Usage is implied by 'the signed-in user's ... projects' – an agent can infer this is the read path for the current user's projects. There is no explicit when-to-use/when-not or prerequisite guidance, and no mention of an alternative to reach other users' or workspace-level projects.

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