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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the return is a 'prose overview of the Kilotest domain, the tool workflow, and links to further documentation', which tells the agent what shape the payload takes. It doesn't state size or whether the overview is static, so it stops short of full transparency.

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?

Four sentences, front-loaded with purpose, then usage rule, then return shape, then domain context. Every sentence carries distinct information with no repetition of the name or annotations.

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?

With no parameters and no output schema, the description carries the burden of describing the return value, and it does so by naming the prose overview, workflow, and documentation links. For an onboarding/explanation tool this is complete enough for an agent to decide to call it and know what to expect.

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 takes zero parameters, so there is no parameter meaning for the description to add and the baseline of 4 applies. The schema is an empty object and the description correctly doesn't invent any inputs.

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 names a specific verb and resource – 'Explains what Kilotest is, what its tools do, and how its results are structured' – and closes with the domain ('tests web pages for front-end quality with an ensemble of rule engines'). That makes it unmistakable against siblings like getReport or listIssues, which operate on test data rather than explaining the system.

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?

It gives an explicit trigger ('Use this before any other tool when the available tools or workflow are unclear') and an explicit exclusion ('it is unnecessary once you know which tool you need'). It also names the alternative set implicitly by pointing at the other tools, leaving nothing for the agent to infer about ordering.

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