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

Annotations already declare the mutation profile (readOnly=false, destructive=true, idempotent=true, openWorld=true). The description adds the useful behavioral constraint that this is a manual owner-attested record, not an automated send. But it says nothing about what gets destroyed or what side effects occur, which is notable given destructiveHint=true on a mere status record.

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 short sentences, front-loaded with the action and followed by the guardrail. Efficient, though the terseness edges into under-specification rather than elegance.

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 destructive-hinted mutation with no output schema and an undocumented required ID parameter, the description should say what state change results, whether it errors if the pitch was already sent (idempotent hint suggests not), and any permission requirement. None of that is present.

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 sole parameter pitchId has 0% schema description coverage and the description provides no meaning for it. With one undocumented required parameter, the description fails to compensate for the coverage gap.

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 concrete verb and resource: recording that a pitch was sent by the owner. The phrasing 'sent this pitch themselves' implicitly distinguishes it from a tool that actually sends the pitch, but it never names the sibling (e.g. soclo_creators_pitch) so the differentiation must be inferred.

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 clause 'Only when the owner says so' gives a genuine gating condition for calling the tool. However, it does not say when to use this instead of the tools that actually send or approve a pitch (soclo_creators_pitch, soclo_creators_pitch_approve, soclo_creators_pitch_replied), so the routing decision is left implied.

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