wisdom_get_agent

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

No annotations are provided, so the description carries the behavioral disclosure burden. It only says 'get,' which implies a read operation, but it does not mention authentication needs, side effects, or what happens when no UUID is provided. It is not misleading, but it adds little beyond the operation name.

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 one short, front-loaded sentence with no filler. It is efficient and easy to parse, though the brevity sacrifices usage and behavioral context that would otherwise support tool selection.

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 single-parameter read tool with no output schema, the description is minimally viable, but it omits what 'agent information' contains and does not mention the current-agent fallback behavior. The fallback is only discoverable in the schema, and the return shape is entirely unspecified.

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%, and the uuid parameter description already documents that it 'uses current agent if not specified.' The tool description adds no parameter-level meaning, so the baseline score of 3 is appropriate.

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 a specific verb and resource: 'Get agent information by UUID.' It is clear that this is a single-agent retrieval operation, and it is implicitly distinguished from wisdom_list_agents by the UUID-based lookup. However, it does not explicitly name sibling alternatives or describe what 'agent information' includes.

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?

The description gives no guidance on when to use this tool versus alternatives like wisdom_list_agents or wisdom_whoami. The only usage hint, that omitting uuid uses the current agent, is in the parameter schema rather than the tool description.

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