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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description is fully consistent with them while adding real value: it discloses that nothing is opened or changed, that the return is a step-by-step procedure, and why the official REST API is not used (paid partner contract). What it does not explain is how it resolves which submission/status is being discussed when it accepts zero inputs.

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 most decision-relevant fact — that this returns instructions and performs nothing — is buried mid-sentence after a lengthy preamble about ChatGPT, Claude and any AI agent. The final sentence about Bullhorn's partner-contract API is useful justification but is verbose for the invocation decision.

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 guidance tool with no output schema, the description covers what it returns (screens, buttons, fields), what it does not do (open anything), and what to do next (cotlet_browser_* tools). The remaining gap is the input side: no explanation of how the target submission and desired status are conveyed.

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?

With zero parameters and no arguments to document, the baseline is met simply by not misleading about inputs. However, the absence of any statement about how the tool infers the submission and target status (presumably from conversation context) leaves the input contract implicit rather than explained.

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 is explicit about the unusual nature of the tool: it 'Returns how to do it in Bullhorn step by step (screens, buttons, fields) and opens nothing by itself', which corrects the misleadingly action-oriented name 'update_submission_status'. It also names the follow-up family (cotlet_browser_* tools in the user's Bullhorn Cloud Browser). It stops short of pointing at a specific single sibling, but it clearly separates itself from the actual executor tools.

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 usage context and a next-step chain: call this to get the procedure, then perform it with cotlet_browser_* tools against the user's Bullhorn Cloud Browser. It does not state when NOT to use it, nor how the target submission/status is conveyed given the tool takes no arguments, which is the one guidance gap.

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