List Manpower Logs Contact Options

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds endpoint details, pagination behavior, and permission-based results, which provide some additional context 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?

The description is moderately concise but contains redundancy (pagination mentioned twice) and a confusing mix of 'Contacts' and 'Daily Log records'. The main purpose is front-loaded, but the inconsistency hurts clarity.

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?

The description lacks important details: no description of the response structure (fields in a contact option object), and the confusion between contacts and daily log records undermines completeness. Since output schema is absent, the description should elaborate on what the returned objects contain.

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?

Input schema already describes all parameters (100% coverage). The description adds usage context for pagination parameters and highlights project_id as required, adding moderate value beyond 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 states that it returns contacts for a manpower log, but then confuses by saying 'Use this to enumerate Daily Log records' and mentions 'paginated JSON array of Daily Log records', which is inconsistent with the title and first sentence. The purpose is mostly clear but muddled.

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 gives vague usage guidance ('when you need a paginated overview, to find IDs, or to filter by query parameters') but does not differentiate this tool from siblings like 'list_manpower_logs' or 'list_manpower_logs_vendor_options'. No explicit when-not-to-use or alternatives.

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