neon3_ui_snapshot

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

The description implies a read-only operation via the verb 'Read,' which is a behavioral hint, and it lists what is included in the snapshot. However, with no annotations, it does not disclose potential errors, side effects, or any constraints such as required authorization. The extra detail about contents adds some transparency, but it remains thin.

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, front-loaded sentence that quickly states the core action and its scope. There is no extra wording or redundancy; every word contributes to the meaning.

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?

Given a parameter that is unexplained and no output schema, the description leaves significant gaps. An agent would not know how to supply the ui_endpoint or what to expect in return, making the tool under-specified for a single-parameter 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?

The schema has a single parameter 'ui_endpoint' with no description (coverage 0%), and the description does not mention or explain this parameter at all. With no compensation from the description, an agent cannot know what value to provide or what effect it has.

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 clearly states the action ('Read') and the resource ('current UI runtime snapshot'), and adds specificity by mentioning 'active fragment and input revisions.' It does not explicitly name a sibling tool for differentiation, but the verb and resource are concrete enough to convey the tool's purpose.

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 guidance on when to use this tool versus siblings. The description says nothing about context, prerequisites, or alternatives, leaving the agent to infer usage from the name and siblings alone.

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