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

With no annotations provided, the description carries the full behavioral burden and handles it thoroughly. It discloses idempotency ('recording the same directory again updates that record rather than adding another'), the fact that nothing is ever deleted, authentication requirements (MCP_API_KEY bearer token), the confirmation-before-writing behavior, and the three status semantics. This goes well beyond a typical terse mutation description.

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 compact paragraph with no filler. Each sentence earns its place: core side effect, status semantics, optional inputs, idempotency, non-submission clarification, and auth/confirmation prerequisite. It is front-loaded with the most decision-relevant information and remains readable despite its density.

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 mutation tool with five parameters, no annotations, and no output schema, the description is unusually complete. It covers purpose, side effects, idempotency, deletion behavior, authentication, confirmation, status meanings, and integration with sibling tools. Nothing essential to deciding whether and how to call this tool is missing.

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 100%, so the schema already documents every parameter fully. The description restates status values and optional URL/note only at a high level. It adds one useful behavioral constraint tied to a parameter ('Idempotent per product+directory'), but it does not significantly augment the per-parameter meanings beyond what the input schema already provides.

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 states a precise verb and resource: 'Record that one of your tracked products has been submitted to a directory.' It also explains the downstream effect on sibling tools ('so check_submission_readiness and generate_submission_kit stop listing it as remaining') and explicitly distinguishes what it does not do ('This does NOT submit anything anywhere'). This makes the tool's purpose unmistakable and well differentiated.

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 clear when-to-use context: after a submission has happened, to prevent duplicate resubmission. It also provides a when-not-to-use boundary ('does NOT submit anything anywhere'), and explicitly ties the tool's effect to check_submission_readiness and generate_submission_kit. This is sufficient guidance for an agent to choose it over related tracking tools.

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