List Bid Packages

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

Annotations already declare readOnlyHint true, destructiveHint false, idempotentHint true. The description adds behavioral details: returns paginated JSON array with metadata, requires project_id, and specifies API endpoint. No contradiction; supplements annotations well.

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 concise (3 sentences) and front-loaded with purpose. Includes possibly extra details like API endpoint, but generally efficient. Not overly verbose.

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?

For a list tool with 7 params and no output schema, the description explains pagination, required parameter, and return type. Annotations cover safety. Lacks details on output fields but remains adequate for selection and invocation.

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 covers all 7 parameters with individual descriptions (100% coverage). Description adds minimal value by mentioning pagination control and required project_id, but largely repeats schema info. Baseline 3 applies.

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 starts with 'Return a list of all Bid Packages for a Project.' clearly stating the verb and resource. It also distinguishes from siblings like list_bid_packages_company and show_bid_package_project by specifying project scope and paginated overview.

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 explicitly says 'Use this to enumerate Bid Management records when you need a paginated overview, to find IDs, or to filter by query parameters.' It provides context for when to use but does not mention when not to use or alternatives like show_bid_package_project.

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