PAIDEIA__pattern_lookup

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

No annotations are provided, so the description carries full burden. It only says 'Filter course-index/patterns.md', implying a read operation, but fails to disclose any other behavioral traits such as error handling, rate limits, authorization needs, or side effects.

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 concise with two sentences, no fluff. However, it could be better structured with separate lines for purpose and usage. Still, it earns its place.

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?

With 3 parameters (none required), no output schema, and low schema coverage, the description should provide comprehensive guidance. It does not explain input parameters, return format, or how to interpret results, making it insufficient for an agent to use the tool correctly.

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 only 33% (only project_root has a description). The description hints that 'Pk label or keyword' relates to the query parameter, but does not explain max_chars or project_root. No additional meaning is added over the schema for the other parameters.

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?

Clearly states it is a namespace alias for pattern_lookup and that it filters course-index/patterns.md by 'Pk label or keyword'. The purpose is specific and distinguishes it from its sibling pattern_lookup by clarifying its role as an alias.

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?

Only mentions 'Use this exact name when Alt searches for PAIDEIA__pattern_lookup', which is a naming instruction. Does not provide guidance on when to use this tool vs alternatives (e.g., pattern_lookup) or when not to use it.

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