Bulk Retrieve Managed Equipment

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

Annotations already provide destructiveHint=false and readOnlyHint=false. Description adds that it is a PATCH operation, returns modified object, and requires company_id. No additional context on rate limits, authorization, or error handling. Adds moderate value beyond 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?

Two sentences plus API details; overall concise. Some redundancy ('Required parameters: company_id' already in schema) but no fluff. Front-loaded with action and usage.

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?

No output schema exists; description only says 'returns the modified object on success'. Lacks details on error handling, batch limits, or whether partial success is possible. For a bulk operation, more completeness expected.

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 100% for both parameters. Description repeats that company_id is required and lists the endpoint, but adds no new meaning beyond what the schema provides. Baseline 3 as per guidelines.

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?

Description clearly states the action as 'Restore multiple Managed Equipment' and indicates it updates existing records via a PATCH endpoint. The name 'bulk_retrieve' is misleading since the tool actually performs a restore/update, but the description corrects this. Distinguishes from sibling tools like bulk_delete_managed_equipment.

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?

Implies usage for updating existing Field Productivity records with only supplied fields changed, but lacks explicit 'when to use' vs alternatives or exclusions. No guidance on when not to use this tool.

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