get_agent_instructions

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool's purpose but does not mention any side effects, safety profile, or whether the instructions are cached or dynamic. For a simple read-only getter this is acceptable, but it adds no contextual information beyond the action itself.

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 a single, focused sentence that front-loads the purpose and lists the three content categories. No wasted words, and the structure supports quick parsing.

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 tool is simple with no parameters, no output schema, and no annotations, but the description does not fully disambiguate from overlapping sibling tools like 'jsdoc' or 'get_custom_rules'. It covers the core content areas but may leave an agent unsure about the exact scope or relationship to other docs tools.

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?

There are zero parameters, so the description is not required to explain parameter semantics. The baseline for no parameters is 4, and the description also clarifies the content of the result, which adds value beyond the schema's empty properties.

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 uses the specific verb 'Get' and identifies a concrete resource: coding guidelines, architectural standards, and JSDoc rules for the project. This clearly distinguishes it from sibling tools like get_usage_guide or get_custom_rules by naming the exact content domains.

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 implies use when the agent needs project-level coding standards, but it does not explicitly state when to choose this tool over alternatives such as 'docs' or 'jsdoc'. No exclusions or alternative recommendations are given, so the guidance is present but implicit.

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