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

With no annotations provided, the description must carry the full burden of disclosing behavior. It only mentions 'Browser-based tool' and '3 format styles', but does not explain how the user interacts with it, what inputs are required, what output is produced (e.g., PDF, HTML), or any side effects. This is a significant gap for a tool with zero annotation coverage.

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 extremely concise, consisting of a single sentence plus a parenthetical. Both pieces of information ('Professional CV in 3 format styles' and 'Browser-based tool') are relevant and non-redundant. It is front-loaded and every word earns its place.

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?

Despite having no parameters and no output schema, the description leaves major gaps: it does not explain what 'career history' refers to, how the tool is invoked (despite claiming browser-based), what the output looks like, or how it differs from the similar 'resume-generator' sibling. This makes the tool under-specified for an agent to use reliably.

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 is trivially 100% covered. The description adds context by mentioning '3 format styles', which is an output characteristic rather than a parameter. Since there are no parameter semantics to explain, the baseline of 4 is appropriate.

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 'Professional CV in 3 format styles' clearly identifies the tool as producing CVs and specifies a concrete scope (three styles). It is not a tautology, but it does not explicitly differentiate from the sibling tool 'resume-generator', which likely has overlapping purpose.

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 no guidance on when to use this tool versus alternative tools like 'resume-generator' or any other CV-related tool. It lacks both inclusion criteria and exclusions, leaving the agent without context for tool selection.

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