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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds important context: 'writes no files and uses no network' and 'format changes rendering without changing content.' This enriches the agent's understanding of side effects and idempotent behavior.

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 concise and well-structured: it opens with purpose, then usage, inputs, and effects. However, the input section is inaccurate, which slightly undermines the structure's usefulness despite its brevity.

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?

The description covers purpose, usage, and effects, and an output schema exists, so return values need not be detailed. However, the input mismatch is a significant gap that prevents full completeness, leaving the agent uncertain about how to supply the correct parameters.

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 description references 'cwd' and 'format' as inputs, but these do not appear in the input schema, which lists platform, projectName, and expectedVersion. This mismatch can mislead the agent into thinking parameters exist that don't. The schema has full descriptions, so the baseline is 3, but the misleading input references reduce clarity.

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 the tool returns a compact operating memory and explicitly distinguishes it from sibling tool axint.context.docs by noting the latter is for longer workflow docs. The verb 'Return' and resource identification are specific and unambiguous.

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 states when to use this tool (after compaction, session restart, long coding drift) and provides an alternative (context.docs for longer docs). This gives the agent clear decision criteria for tool selection.

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