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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaning by stating explicitly that the tool 'opens nothing by itself' and only returns instructions, which prevents the agent from assuming a browser action or write occurs; it doesn't cover prerequisites such as account connection, but for a zero-parameter read tool that's minor.

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?

Three sentences, each doing something, but the ordering is awkward: the action-implying opening sentence arrives before the clarifying one that contradicts it. The final sentence about ConnectWise's REST API and the absence of an MCP server is background justification rather than operational guidance the agent needs to invoke the tool correctly.

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 zero-parameter, read-only documentation tool with no output schema, the definition covers what is returned (steps with screens, buttons, fields) and what to do next (cotlet_browser_* tools). The absence of any statement about required account or browser-session setup is the main remaining gap, but the definition is largely self-sufficient.

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 schema has zero parameters at 100% coverage, so there is nothing the description needs to disambiguate. The description adds no parameter-level semantics, but none are needed, and the baseline for a parameterless tool is 4.

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 (time entry in ConnectWise) and then clarifies that the tool doesn't execute the action: it 'returns how to do it in ConnectWise step by step (screens, buttons, fields) and opens nothing by itself.' This is enough for an agent to understand it's a procedural guide rather than a mutation, although the leading sentence 'Log time entry...' mirrors the action-verb name and creates a moment of ambiguity before the second sentence resolves it.

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?

It gives a clear follow-up route: 'then do it with the cotlet_browser_* tools in the user's ConnectWise Cloud Browser.' That's real routing guidance, but nothing says when not to call this tool, whether a ConnectWise connection or Cloud Browser session is a prerequisite, or how this relates to the other connectwise_* siblings. Usage is implied more than fully specified.

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