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

No annotations are provided, so the description carries the full burden. It does specify the scope ('all') and output fields, but it does not explicitly state that this is a read-only operation or disclose potential side effects, pagination, or authentication requirements. This is a minor gap for a simple listing tool.

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, front-loaded sentence with no superfluous words. It efficiently captures the action, scope, and output fields.

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 parameterless list tool with an output schema, the description is complete enough. It specifies what is returned and the scope. Minor omissions like sorting or authorization are unlikely to be necessary for this simple read-only operation.

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?

The tool has zero parameters, so the description adds no parameter-level meaning, but none is needed. The baseline for zero parameters is 4, and the description adequately covers the tool's behavior without parameter details.

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 the action ('Return all'), the resource ('portfolio projects'), and the specific fields returned ('slug, title, and short description'). It distinguishes this tool from siblings like get_project (singular) and list_posts (different resource type).

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 implicitly communicates that this tool is for retrieving all projects, which is clear context for when to use it. However, it does not explicitly mention alternatives or when not to use it, such as referencing get_project for a single project.

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