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

The readOnlyHint annotation already covers safety, and the description adds meaningful behavior: pagination, sortability, the canonical name fallback chain (operator-set, site brand, niche name), and the precise meaning of lastActivityAt. This goes well beyond the annotation without contradicting it.

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 dense but every sentence adds value: purpose, pagination/sorting, canonical name semantics, and recency meaning. It is front-loaded with the core action and avoids fluff, though the field semantics could be seen as slightly verbose relative to a simple list tool.

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 paginated read-only list with no output schema, the description provides key semantic anchors: name is the canonical identifier, niche.name is distinct metadata, and lastActivityAt drives disambiguation. It omits the default sort order and full response shape, but the essential decision-making context is present.

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?

With 0% schema description coverage, the description must compensate. It explains the sorting values (createdAt, niche, industry) and mentions pagination, but it doesn't explain how cursor works or what limit's default/maximum implies. The sorting semantics are covered; the other two parameters are only implied.

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 starts with 'List all projects for the authenticated operator', giving a specific verb, resource, and scope. It also states pagination and sortable fields, making the tool's behavior clear and distinguishing it from singular get_project or create_project siblings.

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 provides a concrete usage heuristic: when the operator refers to 'my project' without naming one, use the project with the highest lastActivityAt. It doesn't explicitly name alternatives or exclusions, but this rule gives actionable context for selecting the right project from the list.

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