get_bulk_upload_instructions

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

With no annotations, the description bears full responsibility for behavioral transparency. It describes a read operation ('Get') but does not disclose any behavioral traits such as authentication requirements, rate limits, data freshness, or side effects. The description is too terse to inform the agent about safety or side effects.

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 only one sentence, which is concise, but it lacks crucial information such as parameter details and usage context. It sacrifices completeness for brevity, making it insufficiently informative for an agent. The structure is simple but not well-calibrated to the tool's needs.

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?

Given the tool has 1 parameter and no output schema, the description should fully explain the input and output. It fails to describe the return format of the instructions, does not clarify that the platform must be selected from the enum, and provides no context about the bulk upload process. The description is incomplete and relies on the agent's prior knowledge.

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 the single parameter 'platform'. The description does not mention the parameter at all, despite it being required and an enum. It only vaguely references 'a GMP platform', failing to add meaning beyond the schema's enum values. This leaves the agent without guidance on how to fill the parameter.

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 clearly identifies the tool's purpose: to retrieve step-by-step upload instructions and file naming requirements for a GMP platform's bulk upload format. The verb 'Get' and the specific resource 'upload instructions' make the action and object clear. However, it does not distinguish from the sibling tool 'get_bulk_upload_schema', which could be confused as providing similar schema information.

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 provides no guidance on when to use this tool versus alternatives like 'get_bulk_upload_schema' or 'list_bulk_upload_platforms'. There is no mention of prerequisites, context, or conditions under which this tool should be invoked.

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