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

No annotations are provided, so the description carries the full burden. It discloses that this is a read operation ('load') and emphasizes the workflow sequence, but lacks details on behavioral traits like error handling, response format, or performance. It adds some context (e.g., 'to avoid errors'), but is minimal for a tool with no annotation coverage, resulting in an average score.

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 front-loaded with the core purpose in the first sentence, followed by structured instructions. It uses bullet points effectively but includes some redundancy (e.g., repeating the importance of calling first). Overall, it's efficient with minimal waste, though could be slightly more streamlined.

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 the tool's complexity (simple, no parameters) and lack of annotations or output schema, the description is reasonably complete. It covers purpose, usage sequence, and importance, but could improve by detailing the workflow content or potential outputs. It's sufficient for basic understanding but not exhaustive.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate. A baseline of 4 is applied as it compensates adequately for the lack of parameters by focusing on usage context.

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's purpose: 'Load essential spec workflow instructions to guide feature development from idea to implementation.' It specifies the verb ('load'), resource ('workflow instructions'), and scope ('feature development from idea to implementation'). However, it doesn't explicitly distinguish from sibling tools like 'steering-guide' or 'spec-status', which might also provide guidance, keeping it from a perfect score.

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 provides explicit usage guidelines: 'Call this tool FIRST when users request spec creation, feature development, or mention specifications' and 'Always load before any other spec tools to ensure proper workflow understanding.' It specifies when to use (for spec-related requests) and when not to use (after other spec tools), with a clear sequence requirement, earning the highest score.

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