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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds that it returns a structured, audited deliverable and validates inputs server-side, providing useful context beyond the annotations. There is no contradiction.

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 longer than necessary, containing branding noise ('Gapup agent-payable C-suite expertise (RISK)') and a list of example questions that could be condensed. It front-loads the purpose but could be more tightly structured.

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 9 parameters and no output schema, the description provides a reasonable overview and usage examples, but lacks details on the deliverable's structure, how to interpret estimates, and edge-case behavior. The validation note is helpful but does not fully compensate for the missing output schema and under-documented parameters.

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 description coverage is only 11%, so the description must compensate. It adds meaning via placeholders like <scope_type>, <tech_stack>, and <N> assets, plus a reference case (Acme SaaS, web-app, Node.js AWS) that maps to several parameters. However, it does not clarify all parameters; target_geos, retest_included, and async are not addressed.

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 identifies the tool as a pentest scope estimator, with specific examples of the questions it answers (effort/cost estimates, budget, engagement plan, engagement type, prerequisites/risks). It distinguishes itself from sibling tools by focusing on pentest scoping/estimation rather than vulnerability scanning or attack surface monitoring.

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 multiple concrete usage scenarios via example questions, such as budgeting for SOC 2 compliance and choosing engagement types. It gives clear context for when to use the tool but does not explicitly mention when not to use it or name alternatives.

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