score_bid_fit

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions the return type (score + recommendation) but does not state whether the tool is read-only, has side effects, or requires specific permissions. The absence of contradictions is noted.

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 concise: a one-line purpose statement followed by a clean parameter list. Every sentence adds value, no redundancy. The structure is front-loaded with the primary action.

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 has 5 parameters, no annotations, and an output schema (implied by mentioning score), the description covers purpose, all parameters, and return value. It also references a sibling tool (manage_company_profile) for context. No gaps are apparent.

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 0%, so the description must compensate. It provides detailed explanations for all 5 parameters, including the structure of inline_profile (dict with licenses, certifications, revenue, prior_contracts) and the relationship between profile_id and manage_company_profile. This adds significant meaning beyond the schema's titles and types.

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 the tool evaluates bid fit by matching company profile (licenses, revenue, performance) with notice requirements and outputs a 0-100 score plus recommendation. This specific verb-resource combination distinguishes it from siblings like analyze_competitor or manage_company_profile.

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 when a company profile and bid notice are available, and explicitly mentions that profile_id is stored via manage_company_profile, indicating a prerequisite. However, it does not explicitly state when not to use or compare to alternatives like analyze_competitor.

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