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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower, yet the description adds genuinely useful behavior: it renders an interactive card with buttons that copy pasteable requests, and it returns a specific one-line fact set (version, save time, comment count, kept applications by status, noResponse count). That is real disclosure beyond the structured fields, though it does not say how statuses are enumerated or what the card renders on non-client surfaces.

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 purpose is front-loaded, but the middle clause — 'a card in the conversation on clients with interactive views' — is grammatically tangled and takes effort to parse, and the description runs long for a zero-parameter tool. Roughly half the text earns its place; the rest could be tightened without losing meaning.

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 the return value, and it does so concretely by enumerating the facts in the summary line. Annotations cover the safety profile and there are no parameters to document, so the only shortfall is that terms like 'kept' and 'noResponse' are used without definition.

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 schema takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the tool needs no input to produce its summary.

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 ('Show the person Graphlog Career's home') and clarifies that this renders an overview card plus a one-line facts summary, so the agent knows it is a dashboard-style read rather than a record fetch. It never contrasts itself with close siblings like show_career_record or get_career_record, which is the remaining gap.

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 one concrete trigger: 'It serves a message that is just "Graphlog"', which tells the agent when this tool is the expected handler. Beyond that there is no guidance on when to prefer it over list_career_applications or get_career_record, and no exclusions or prerequisites are stated.

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