Get context pack

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

No annotations are provided, so the description carries full burden. It discloses the return content comprehensively (pinned guidance, lessons, exemplars, tone notes, outcome stats) and mentions response format options ('md' vs 'json'). It does not cover side effects, auth, or rate limits, but for a read-only fetch tool, the disclosure is 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 two sentences with zero wasted words. The first sentence lists the payload components concisely, and the second provides a critical usage instruction. It is front-loaded and efficiently structured.

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?

Despite having no output schema, the description thoroughly explains what the return value contains by listing multiple specific items. It does not mention pagination or error handling, but for a 'get' tool that returns a context snapshot for drafting, the level of detail is sufficient.

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% as both 'format' and 'platform' have descriptions. The description adds marginal value by stating that 'md' is best for reading, which is helpful but not essential. Baseline 3 is appropriate since schema already explains the parameters well.

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 uses a specific verb 'Fetch' and resource 'full learning payload for a platform'. It lists detailed components (pinned guidance, lessons, exemplars, etc.) which clearly distinguishes it from sibling tools like analytics_get, briefs_get, etc. The instruction 'CALL THIS FIRST' further clarifies its unique role.

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 explicitly says 'CALL THIS FIRST, before drafting anything', providing clear context for when to use the tool. While it doesn't explicitly list when not to use it or name alternatives, the instruction implies it's a prerequisite for drafting, which is sufficient guidance.

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