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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one piece of behavioral context beyond that — results are privacy-filtered — but says nothing about scope, latency, or what 'status' includes.

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 short sentence, so nothing is bloated, but 'Read hosted' is redundant filler before an already-restated tool name, and the sentence is not front-loaded with anything genuinely informative.

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 and three parameters, the description should at least clarify what a 'status' result contains and how sessionId/executionId scope the read. It does neither, leaving the duplicated schema parameter descriptions as the only guidance.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter meaning of its own, and notably does not clarify sessionId or executionId, whose schema descriptions are copy-pasted projectId text.

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 'Read hosted get project status using privacy-filtered project metadata' essentially restates the tool name rather than describing the operation in a distinguishable way. With siblings like get_project_sync_status, get_project_health, and get_agent_execution_status, an agent gets no basis to tell this tool apart from them.

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?

There is no statement of when to use this tool versus get_project_health or get_project_sync_status, and no prerequisites or exclusions are given. The only guidance present ('privacy-filtered') is a qualifier, not a usage condition.

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