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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description earns credit by documenting the return payload in detail (branchViewOnly, motionTimeline, planLimits, unsavedFiles, imported/CONVERTED.md) for a tool with no output schema, which is exactly the behavioral context annotations cannot supply. It says nothing about behavior for a bad or unfamiliar projectId, so it is not a 5.

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?

It is a single enormous run-on sentence shot through with nested parentheses, listing roughly a dozen return fields with sub-parentheticals inside parentheticals. The front-loaded framing and the trailing usage instruction are well placed, but the middle is a wall of text an agent must parse rather than scan, and several clauses repeat themselves (branch/branchViewOnly, plan/page limits).

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 one required param, no output schema, and a broad aggregate read, the description does the heavy lifting by telling the agent what comes back and which decisions it informs. Only error/empty-case behavior and the relationship to sibling reads are left out, which is a modest gap for this complexity level.

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?

There is one parameter and schema description coverage is 100%; the schema already says "Project id from list_projects". The description adds no format, sourcing, or failure semantics beyond that, so the baseline of 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?

The description opens by framing the tool as a read of everything known about one project, then enumerates the concrete payload categories (framework, styling, CMS, plan limits, draft changes). The verb is soft ("What Xodia knows about") and the actual purpose is buried under field enumeration, but the resource and scope are unmistakable and separable from list_projects or get_collection.

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?

It gives two concrete triggering conditions: call it first on an imported or converted site, and before planning new pages or collections. That is real when-to-use guidance rather than implied context. It stops short of naming alternatives or stating when not to call it (e.g. versus list_projects for discovery), which keeps it from a 5.

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