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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavioral context beyond them: figures are the latest sample, and disk sizes and the day's traffic lag a few minutes. That staleness caveat is exactly the kind of detail an agent cannot get from structured fields.

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?

A single dense sentence that front-loads 'Start here' and then lists returned content, followed by the freshness caveat. The enumeration is long but each item maps to real content the caller will receive, so little is wasted.

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 output schema, the description carries the burden of describing return contents, and it does so by enumerating the main sections plus the freshness caveat. It omits nothing critical for a zero-argument orientation tool, though it does not hint at response shape or size.

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 the baseline is 4; there is nothing for the description to disambiguate. The schema accepts an empty object with additionalProperties false, which is consistent with a no-argument read.

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?

States a specific verb-plus-resource ('the machine') and then enumerates exactly what it returns: resources, the person's domain, backups, SSH, every project with problems and URL, deleted projects with snapshots, GitHub repos. This makes it clearly distinguishable from narrower siblings like GetProject or ListCommits.

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?

'Start here' is an explicit entry-point directive that tells the agent when to reach for this tool first. It stops short of naming alternatives or stating when-not to use it (e.g. vs GetProject for a single project), so it is clear but not fully routing-aware.

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