llm_instructions_get

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

No annotations are provided, so the description carries full burden. It mentions retrieval but doesn't disclose behavioral traits like authentication needs, rate limits, response format, or potential side effects. The guidance to use it first hints at initialization, but lacks detail on what the instructions contain or how they affect subsequent tool usage.

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 concise sentences with zero waste. It's front-loaded with the purpose and followed by usage guidance, making it highly efficient and well-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?

Given no annotations, 0% schema coverage, no output schema, and a parameter-heavy context (1 required param), the description is incomplete. It lacks details on parameters, return values, and behavioral aspects, making it insufficient for an agent to use the tool effectively beyond the high-level guidance.

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 0%, and the description provides no information about the single required parameter 'kwargs'. It doesn't explain what 'kwargs' represents, its format, or how it should be used, leaving the parameter completely undocumented.

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 verb 'retrieve' and the resource 'LLM usage instructions for the Sentinel MCP Server'. It specifies what the tool does, though it doesn't explicitly differentiate from sibling tools, which are unrelated to LLM instructions.

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 'Use this tool first before all other tools', providing clear when-to-use guidance. It implies this is a prerequisite for other operations, though it doesn't name specific alternatives or exclusions.

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