Get agent instructions bundle

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds the HTTP method (GET) and authorization class, offering mild behavioral context. However, it does not disclose potential implications like whether the bundle includes resolved templates or raw content.

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 very short (two sentences) and front-loaded with the main purpose. However, the first sentence repeats the title, and the second provides operation details. It is efficient but misses an opportunity to include parameter context without becoming verbose.

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 read-only tool with one parameter and strong annotations, the description is mostly adequate. However, the lack of parameter explanation and any description of the output (despite an output schema existing) reduces completeness. The tool is easy to use if the agent understands 'id'.

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 input schema has one required parameter (path.id) with 0% description coverage in the schema. The description does not mention or explain this parameter, leaving the agent to infer that 'id' likely refers to the agent ID. This is a significant gap.

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 states 'Get agent instructions bundle', specifying the verb 'Get' and the resource 'agent instructions bundle'. This distinguishes it from sibling tools like 'pc_patch_agents_by_id_instructions_bundle' (patch) and 'pc_get_agents_by_id_instructions_bundle_file' (file-specific retrieval).

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. The description mentions authorization class ('board_or_agent') but does not explain contexts where this retrieval is appropriate or when to use related tools like the file- or patch-based endpoints.

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