neon3_project_assets

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

No annotations are provided, so the description carries the full burden. It does state 'Read', which suggests a safe read operation, but it does not disclose endpoint behavior, error conditions, output format, or any other side effects. The word 'stable' hints at output behavior but is too vague to provide meaningful transparency.

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, direct sentence with no filler. It front-loads the action and object and is appropriately concise for a tool with one optional parameter.

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?

There is no output schema, no annotation, and no endpoint or usage context. An agent is left without enough detail about how to supply 'projectd_endpoint', what 'projectd' refers to, or how this tool fits alongside the many related sibling tools. The bare statement of what it reads is not enough for reliable selection and invocation.

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%, and the description never mentions 'projectd_endpoint' or explains how it should be used, whether it is optional in practice, or what format it should take. The schema only provides the property name, type, and minLength, so the description adds no parameter-level meaning.

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 uses a clear verb ('Read') and names specific resources ('project summary', 'stable AssetRef entries') plus the source ('projectd'). It is reasonably distinguishable from sibling tools like the nui_* and app_* tools, though it does not explicitly contrast itself with 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 guidance about when to use this tool versus its siblings, nor any stated conditions, prerequisites, or exclusions. The intended usage must be inferred entirely from the tool name and the one-line description.

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