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

Annotations already declare readOnlyHint=true/destructiveHint=false, so safety is covered, and the description adds real behavioral context beyond them: newest-first ordering, a 100-per-page cap, and the Cotlet API key auth prerequisite with app-scope requirement. It does not mention pagination semantics via cursor, but the added auth and page-size details are meaningful.

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?

Front-loaded with the resource and return fields, and most sentences earn their place. The opening fragment 'Houzz Pro: Projects with client, address and status' is slightly telegraphic, and the ordering/fields are mildly redundant, keeping it from a 5.

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?

With no output schema, the description adequately conveys what comes back (client name, address, status) and the pagination shape (events capped at 100 per page, cursor-based). Auth requirements are also stated. Minor gap: it doesn't explicitly tie the cursor parameter to the 'next page' workflow, but coverage is solid for a list tool.

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 coverage is 100%, so all three parameters are already documented. The description restates the page cap (matching the limit schema) and the query behavior (matching the query schema) but adds nothing beyond what the schema already provides. Baseline 3 is appropriate.

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 ('Lists your projects') plus the returned fields (client name, address, status) and ordering ('newest first'). Within the houzz-pro sibling set this is the only list_projects tool, so no disambiguation is needed, but the scope is unambiguous.

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?

Gives clear operating context: search by project or client name, and 'Use the project_id with the estimate, invoice, task and time tools' routes the agent to downstream consumers. No explicit when-not or alternative, but the pattern here is a straightforward list call.

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