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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by scoping what is and is not returned ('The conversation isn't included'), preventing an agent from assuming it can read transcripts after this call. No auth or rate-limit context is added, keeping it short of a 5.

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?

Two sentences, zero filler. The positive return list is front-loaded and the exclusion clause is placed last where it reads as a caveat rather than a delay.

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?

There is no output schema, so the description bears the burden of describing return values – and it does so explicitly by enumerating state, model, profile, config ID, activity enum values, machines, and MCP connection states, plus the negative 'conversation isn't included'. For a simple, fully-documented-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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% – all three identifiers are documented with their org_/agt_/proj_ prefixes and regex patterns – so the schema carries parameter semantics. The description adds nothing about parameter meaning or interaction, which is the correct baseline of 3 when the schema does the heavy lifting.

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?

States a specific verb+resource ('Returns one agent's state, model, profile...') and enumerates the exact fields returned, which is far more informative than a generic 'get'. The word 'one' implicitly separates it from agents_list, so an agent can distinguish the two without opening schemas.

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 by the shape of the tool (fetch a single agent), but there is no explicit when-to-use guidance, no prerequisite note (e.g., that agentID/orgID/projectID must come from agents_list or a launch call), and no mention of siblings like agents_events_list as alternatives for activity history.

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