neurogenesis__get_agent

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

With no annotations, the description must convey behavioral traits. It only lists returned components but does not mention read-only nature, potential performance impact, response size, or any side effects. 'Full current state' is vague and lacks specifics.

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 includes an extraneous bracketed prefix ('neurogenesis — developmental agents...') that seems like a module header rather than tool-specific info, adding noise. The actual functional description is a single sentence, but the tool would benefit from a more structured, parameter-focused format.

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 absence of output schema and the tool's complexity within a large module, the description fails to explain the meaning of 'genome', 'cognitive graph', 'trust', or the structure of the response. It does not address automation needs like pagination, filtering, or error conditions.

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 coverage is 0%, so the description must add meaning. It does not describe the 'agent_id' parameter at all—no format, constraints, or how to obtain it. The description focuses solely on output, ignoring input semantics.

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 the tool returns the 'full current state' including genome, cognitive graph, and summary counts, which clearly indicates what it retrieves. The bracketed prefix is confusing but does not obscure the purpose. It distinguishes from sibling tool 'neurogenesis__describe_agent' by implying a more comprehensive output.

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 guidance on when to use this tool versus alternatives like 'describe_agent' or 'list_agents'. The description does not mention prerequisites, conditions, or preferred scenarios for invoking get_agent.

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