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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description's "Read-only" restates it, while "free" adds a genuine cost signal not present in structured data. It discloses what data is returned but says nothing about freshness guarantees, pagination, or failure behavior.

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 dense sentences, front-loaded with the aggregate scope followed by the optional parameter's effect. Every clause carries distinct information; nothing is filler.

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 carries the return-value burden and does it well by enumerating the state fields returned. Minor gaps remain around output format/shape and whether the project view is additive to the base payload.

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% but the schema text is thin ("Add a project view"); the description expands it meaningfully by specifying that project_id yields that project's sequences, assets, and review-queue length, telling the agent what the parameter actually changes.

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 concrete verb+resource (fetch whole account state) and enumerates the payload: account tier/credits/reset, default models with price, jobs in flight, catalog freshness, project count. That specificity distinguishes it from narrower siblings like lab_get_project or lab_jobs_inflight, though no sibling is named directly.

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?

"One call, the whole picture" implies using this for an overview instead of many targeted calls, and "Pass project_id for that project's sequences, assets and review-queue length" gives conditional guidance for the optional parameter. There is no explicit when-not or named alternative, so usage is only implied.

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