get_agent

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

The description implies a read-only operation (GET). No annotations are available to compensate. It does not disclose error handling or authentication needs, but for a simple retrieval tool, this is minimally adequate.

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 short but includes redundant information (the HTTP endpoint duplicates the tool name). It is not verbose, but could be more efficient by omitting the endpoint line.

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 GET by ID with one parameter and no output schema, the description is complete enough. It lacks details on response format, but that may be acceptable given the tool's simplicity.

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 covers the single 'id' parameter 100%. The description adds no additional meaning beyond what the schema provides (path parameter). This meets the baseline for full schema coverage.

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 'Get Agent' clearly indicates the tool retrieves a single agent. The reference to the HTTP endpoint adds specificity. However, it does not distinguish from the sibling tool 'get_agents' which likely returns all agents.

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 is provided on when to use this tool versus alternatives like 'get_agents' or 'get_current_agent'. There is no information about prerequisites or context.

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