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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description doesn't need to repeat those. It adds 'privacy-filtered project metadata', hinting at a filtering behavior, but it's not specific about what that means for the caller. It doesn't disclose pagination, error cases, or authentication requirements.

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 a single sentence, but it's under-specified rather than concise. It lacks essential information and doesn't front-load the most useful details. It's short but not appropriately sized because it omits crucial context.

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 six parameters, no output schema, and only basic annotations, the description is grossly incomplete. An agent has no idea what 'analyze impact' is, what parameters do, or what to expect in the response. This is far from a minimal viable description.

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 0%, so the description carries the full burden for explaining the six parameters. It only mentions 'project metadata' indirectly, and none of the parameters (projectId, cursor, nodeIds, pageSize, sessionId, executionId) are explained. The description adds no value for parameter understanding.

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 states a verb 'Read' and a resource 'hosted analyze impact', but 'analyze impact' appears to be the tool's own name, making this nearly a tautology. The phrase 'privacy-filtered project metadata' adds context but doesn't clarify what the tool actually does or returns.

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?

No mention of when to use this tool versus other read tools like graph_read or project_read. No alternatives or exclusions are provided, leaving the agent without routing guidance.

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