Generate Career Compass Report (PDF or HTML)

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

Annotations are minimal (readOnlyHint, destructiveHint, idempotentHint false). The description adds value by stating it's a self-knowledge (non-directive) tool, warning about premium cost (~50% of budget), and indicating it generates PDF/HTML. No contradictions with 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?

Description is three sentences plus an example, efficiently covering core purpose, cost, and a usage hint. No fluff, but the example could be more concise. Slightly better than minimal viability.

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?

Lacks description of output format (PDF vs HTML), response structure, or how to specify format. No output schema exists. For a complex report tool, more detail on what the agent can expect would improve completeness.

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 coverage is 100% with descriptions for all 7 parameters. The description does not add additional parameter meaning beyond the example and cost note. Baseline 3 is appropriate since the schema already fully documents 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 clearly states it is a career-themed natal report focusing on MC, 10th-house cusp, Saturn, Mars, and Sun aspects. The title 'Generate Career Compass Report' and the phrase 'Self-knowledge tool, not directive' precisely define its purpose and distinguish it from sibling report tools.

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 includes a cost warning and example, but lacks explicit guidance on when to use vs. alternatives like reports_natal or reports_love. The '[Group: Reports]' tag implies grouping, but no direct comparison or exclusion criteria are provided.

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