mcp_compress_linguistic

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

With no annotations, the description alone bears responsibility for behavioral disclosure. It states 'Additive, CRS homotopy preserving,' which implies non-destructive behavior, but lacks details on safety, idempotency, permissions, or side effects. Some useful context is given but not comprehensive.

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 with two sentences, front-loading the main action and outputs. However, dense jargon ('functor-style', 'VSA', 'mint_linguistic', 'CRS homotopy') reduces clarity. It earns points for brevity but loses some for accessibility.

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?

Given no output schema, the description should explain return values in more detail. It mentions 'crs + compressed preview' but does not define these terms or their structure. For a specialized tool aimed at domain experts, it may suffice, but for a general AI agent it is incomplete.

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 coverage is 100% and the schema already describes both parameters adequately. The description adds minimal extra meaning beyond mentioning 'word/context/discourse,' which is partially redundant. Thus baseline 3 is appropriate.

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 it compresses a LinguisticDiscourseBundle into a phase/payload block and returns a CRS and compressed preview. The verb 'compress' and differentiation from the sibling 'mcp_decompress_linguistic' are evident, though jargon like 'functor-style' and 'CRS homotopy' may obscure meaning for unfamiliar agents.

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 explicit guidance on when to use this tool versus alternatives. It mentions 'Phase 3' implying a sequence, but no prerequisites, caveats, or conditions are provided. The description does not tell the agent when not to use it or what to use instead.

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