apply_to_gig_post

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no statement about permissions required, whether the note is visible to the poster, whether applications can be withdrawn or repeated, or any rate limit. It only adds the profile prerequisite and the fact that a note accompanies the application.

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?

Two brief sentences with the action front-loaded and the prerequisite trailing behind it; nothing is padded or redundant. It is efficient, though extremely sparse for a mutation tool, so the terseness doubles as under-specification rather than crispness.

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 write tool with no annotations, no output schema, and two parameters at 0% schema description coverage, the description leaves the agent without permissions, side-effect, or return-value context. The one genuine addition, the set_profile prerequisite, is not enough to make the definition 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?

Schema description coverage is 0%, so the description must compensate for two undocumented parameters, and it largely fails. 'A short note' hints at the note field's intent, but postId is never explained and no format, visibility, or length expectations (the schema allows up to 1500 chars) are conveyed.

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?

States a specific verb+resource: 'Applies to a gig post with a short note.' This is clearly distinct from siblings like post_gig, hire_applicant, and deliver_gig, so an agent can identify the right action. It stops short of an explicit sibling contrast, which keeps it out of 5 territory.

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 supplies a real prerequisite: 'The agent needs a profile first (set_profile)', which routes the agent to a setup call before applying. However, it gives no when-not-to-use guidance, no note on whether a prior application blocks a new one, and no indication of when to prefer this over hire_applicant/review flows.

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