get_guidance_hub

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

With no annotations provided, the description carries the burden of behavioral transparency. It discloses the notable behavior that an active incarnation will return its specialized hub instead, and states the return type as an MCP response. This goes beyond a simple read-only operation, though it does not cover potential errors 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 compact and front-loaded with the primary purpose. The second sentence reinforces the hub's role but is somewhat redundant with the first. The 'Returns' line is trivially redundant given the output schema, but overall the structure is clear and scannable.

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 simplicity (no parameters, output schema present), the description is complete. It explains the main purpose, the incarnation-specific override, and the return type. There are no missing elements that would prevent an agent from selecting and invoking 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?

The tool has zero parameters, so the schema provides full coverage (100%). The baseline score of 4 applies, and the description does not need to add parameter details. The mention of 'incarnation' behavior indirectly relates to context but does not conflict with the empty schema.

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 states 'Get the AI Guidance Hub content' clearly identifying the verb and resource, and further positions it as 'the central entry point for navigation,' which distinguishes it from sibling tools like get_best_practices and get_current_incarnation. The special-case mention of incarnation-specific hubs adds unique functionality clarity.

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 when to use the tool by describing it as the 'main entry point for AI assistants to understand what capabilities are available,' suggesting it should be invoked for initial navigation. However, it does not explicitly mention alternative tools or provide exclusion criteria, leaving room for more explicit guidance.

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