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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the safety profile is provided. The description adds context annotations cannot: that no external SEO provider is invoked, no credits are consumed, and each result carries `projectCount` — useful for an agent predicting cost and payload shape.

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 tight sentences with the resource, the returned field, and the cost profile front-loaded. Nothing is wasted and no sentence is redundant with the annotations or schema.

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 zero-parameter read tool with no output schema, the description supplies the essential return shape (`projectCount` per portfolio) and the cost model. It omits nothing an agent needs to invoke it, though a note on ordering or emptiness handling would have made it fully self-contained.

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 takes zero parameters, which is the baseline-4 case; nothing needs documenting and the description correctly implies an unfiltered list. No syntax or format detail is required here.

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 (Lists) and resource (the caller organization's portfolios) and even names the payload field returned, `projectCount`. It does not explicitly contrast itself with the sibling `get_portfolio` (single-portfolio fetch), so it stops short of full sibling differentiation.

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 'FREE: database only, no SEO data provider is called and no credits are spent' line is a genuine decision signal for an agent weighing cost, but there is no explicit when-to-use versus when-not-to-use, and no alternative sibling is named. Usage is implied rather than stated.

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