clokio_get_project_contacts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds no behavioral context beyond that. It does not mention whether it returns a list, the shape of the contacts, or behavior for invalid or missing projects, so no extra transparency is provided.

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 a single short sentence that front-loads the core resource with no filler. It earns its place but is slightly under-specified, reading more like a fragment than a full instruction.

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 simple read-only tool with one required parameter, the description gives the essential resource and the relevant project link. However, with no output schema, it leaves the return shape and usage context implicit, making it minimally viable but not complete.

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, but it only implies that project_id identifies a project. It does not explicitly state that project_id is the project whose client's contacts should be fetched, nor does it explain where valid project IDs come from.

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 names the resource ('contacts for a project's client') and pairs with the verb 'get' in the tool name, making the core action clear. It is distinguishable from siblings like clokio_get_client and clokio_add_client_contact, though it does not explicitly say 'list' or 'retrieve'.

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 no guidance on when to use this tool versus alternatives. It does not mention that one should use this when needing client contacts via a project, or point to a sibling like clokio_get_client for client details.

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