upwork_get_unread_count

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

The description discloses that it returns a count, but does not mention that it is a read-only operation, authentication requirements, or performance characteristics. Since no annotations are provided, the description carries the full burden and leaves some gaps.

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 short but contains slight redundancy: 'Get count...' and 'Returns total...' could be merged. It is not overly verbose, but could be more succinct.

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 no output schema, the description clarifies the return value. However, it does not specify data type or error conditions, which would improve completeness for an agent.

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 tool has zero parameters, and schema coverage is 100%. The description adds value by specifying the return value (total unread message count), which is helpful given no output schema. Baseline is 4 for no parameters.

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 gets the count of unread messages, which is specific and distinct from sibling tools like upwork_get_messages that retrieve actual messages.

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 count is needed, but lacks explicit guidance on when not to use or alternatives (e.g., if message contents are needed, use upwork_get_messages).

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