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

No annotations are provided, so the description carries the full burden. It discloses that this is a read-only retrieval (implied by 'Get') and specifies the exact components included in the response (metadata, env, skill, source files). It does not describe error handling, authentication, or side effects, but the return content is a meaningful behavioral disclosure.

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, compact sentence with the primary verb upfront. It enumerates the bundle components efficiently without any redundancy, earning its place for each word.

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 one-parameter get tool, the description provides the core purpose and lists the response contents. However, with no output schema or annotations, it lacks behavioral details such as error responses or permission requirements, and the response structure is only implied, leaving some gaps for an agent.

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 provides only a string parameter 'id' with no description (0% coverage). The description adds that this is for 'one agent', clarifying that 'id' is the agent identifier. It does not provide format constraints or guidance on obtaining the id, but for a single parameter, this is sufficient.

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 specifies the action (Get), the target resource (full bundle for one agent), and enumerates the bundle contents (metadata, env, skill, source files). This distinguishes it from sibling tools like list_agents or search_agents, which would not provide the full bundle.

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 implies this tool is for retrieving the complete data for a single agent, contrasting with list_agents (overview) and search_agents (filtered). However, it does not explicitly name alternatives or state when not to use this tool, but the context is clear enough for an agent to decide.

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