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

No annotations are provided, so the description must bear the burden of behavioral disclosure. It only says 'List', which implies a read operation, but it does not explain ordering, what 'recent' means, whether filtering or pagination applies, or what the response contains.

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 with no filler or redundancy. Every word adds meaning, and the action and scope appear first.

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?

For a simple, one-optional-parameter listing tool, this description is minimally functional. However, with no annotations and no output schema, it leaves the agent to infer response format, 'recent' semantics, and the exact meaning of NEO in this context.

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 one parameter, limit, with a default of 5, but the description does not mention it. Schema description coverage is 0%, so the description should compensate, but it adds no parameter-level meaning beyond the parameter name itself.

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 specific verb ('List') with a clear resource ('Render deploys') and a scope ('for NEO'), making the tool's function immediately obvious. It also distinguishes itself from sibling tools like neo_render_logs and neo_render_status (different resources) and jarvis_render_deploys (different scope).

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 over alternatives such as jarvis_render_deploys, neo_render_logs, or neo_render_status. The description implies a simple listing use case but provides no conditions, exclusions, or routing advice.

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