nexus_get_project

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

With no annotations provided, the description carries the burden of explaining behavior. It correctly states the tool returns a structured summary, implying a read operation, but it does not disclose failure behavior for invalid slugs or confirm there are no side effects. This is a minor gap for a simple getter.

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 wasted words. It communicates the action, resource, and input mechanism efficiently.

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 the tool's simplicity — one required parameter, no nested objects, no output schema — the description and schema together provide enough context for an agent to call it correctly. A bit more detail about the shape of the 'structured summary' would improve completeness, but it is not essential.

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 schema already fully documents the slug parameter. The description only repeats the slug concept without adding format details, edge cases, or additional meaning beyond the schema.

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 verb 'Devolve' (returns) and the specific resource: a structured summary of a Nexus project from a folder slug. It is distinct from sibling tools like nexus_search, nexus_create_draft, and nexus_list_recent, though it does not explicitly name 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?

Usage is implied: call this when you have a Nexus folder slug and want the structured project summary. There is no explicit guidance about when to use an alternative tool like nexus_search when the slug is unknown, so the guidance remains implicit rather than explicit.

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