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

No annotations are provided, so the description carries full transparency burden. It states the tool is for viability detection only, not filing, and that it hands off to CPA/program office. However, it does not disclose any behavioral traits like what happens after screening (e.g., returns a boolean or report), authentication needs, or whether it is read-only.

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 a single sentence that packs essential information about what grants are screened and the non-filing nature. It is front-loaded and free of fluff, though a slightly structured format (e.g., listing grant types) could improve scannability.

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?

Given the tool's 13 parameters, no output schema, and no annotations, the description is critically incomplete. It does not explain what the tool returns, how to interpret results, or how individual parameters (e.g., 'state', 'preRevenue', 'grossReceiptsThisYear') affect the screening outcome.

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 input schema has 13 parameters with 0% description coverage, yet the description mentions none of them by name or role. It vaguely refers to 'activities' but provides no mapping to parameters like 'activityTechnical', 'facedTechnicalUncertainty', or 'grossReceiptsThisYear', leaving the agent without guidance on how to populate the schema.

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 screens eligibility for the federal R&D tax credit (26 U.S.C. 41 4-part test), payroll-tax offset, and SBIR/STTR + state grants. It distinguishes itself from filing services by explicitly noting 'VIABILITY DETECTION ONLY' and that it never takes a percentage, which clarifies its role and differentiates it from sibling tools like 'qualify_check' or 'life_event_scan'.

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 implies usage for eligibility screening of R&D credits and grants, and clarifies it is not a filing service. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor does it compare with sibling tools or specify prerequisites (e.g., requiring a CPA partner).

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