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

The description says 'Read', yet the annotations declare readOnlyHint=false, which is a mild tension the description never resolves (does the read record anything or require a special agent_key?). It adds 'private' as a clue about access scope, but no auth requirements, no rate limits, and no statement about what data comes back.

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?

It is a single short, front-loaded sentence with no wasted words, but its brevity reflects under-specification rather than disciplined concision.

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 tool with two undocumented parameters, no output schema, and only partial annotation coverage, a single vague sentence leaves the agent without enough to invoke it correctly or know what to expect in return.

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% for both agent_key and project_id, and the description explains neither parameter — it never mentions an ID, an agent key, or expected formats. Nothing compensates for the total documentation gap.

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 verb 'Read' and the resources 'product work' and 'agreement' give a rough sense of a retrieval operation, but 'private product work' is fuzzy jargon that doesn't clearly map to a product project record keyed by project_id. It does not distinguish itself from close siblings such as speedbot_product_list, speedbot_product_mine, or speedbot_product_agreement.

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?

There is no statement of when to use this tool versus the many product_* and read_* siblings, and no prerequisites or exclusions. The agent is left to infer the use case entirely.

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