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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds useful behavioral context beyond annotations: the modes ('discover', 'research', 'agent_workflow', 'workflow') and what each mode returns. There is no contradiction between the description and annotations.

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 wellorganized with clear sections: purpose, when to use, modes, and available workflows. Every section contributes to selection and invocation. It is longer than some tool descriptions, but the content is relevant and densely informative rather than verbose.

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 that there is no output schema, the description compensates by stating what is returned and by detailing mode-specific behavior and available workflows. It sufficiently supports correct invocation for a guidance tool, especially with 100% schema coverage and read-only annotations. A slight gap is that it does not describe the exact response structure or interaction pattern, but this is minor for a guide tool.

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 100%, so parameters are already documented. The description adds value beyond the schema by explaining what each mode does in practice and listing available workflows, which helps the agent select an appropriate mode. This exceeds the baseline for fully covered 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?

The description opens with a specific verb and resource: 'Get guidance on how to use Perception's intelligence tools effectively.' It clearly distinguishes this meta-tool from the data-gathering siblings by stating it returns tool overviews, role-specific tips, and multi-step research workflows. The purpose is immediately understandable and not a tautology.

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 an explicit 'WHEN TO USE' section with three concrete scenarios, such as new users asking 'what can you do?' and users wanting a structured research workflow. It gives clear context, but it does not explicitly state 'when not to use' or name alternative sibling tools as fallbacks.

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