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

Annotations already declare a non-read-only, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the submission is persisted and receives a reference number. It says nothing about duplicate submissions, error behavior, or how the reference is returned, which matters for a 10-parameter write.

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 with the core action front-loaded and no filler. The second sentence is vague ("kept with a reference number") but is not wasteful in length.

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 tool with 10 parameters, nested objects, an enum, and no output schema, the description is far too thin: it does not explain the return shape (presumably a reference number), the role of optional blocks like contact or specifications, or when a requirement is rejected. An agent could call it, but only by guessing at most of the payload's structure.

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 only 40%, and the description contributes no parameter meaning at all — no explanation of action, budget, timing, quantity, geography, or requested_fields, and no clarification of the opaque "slug"/"anything-else" convention. With this many nested objects and an enum left undocumented, the description does not compensate for the schema 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?

The description states a specific verb ("Send") and resource ("a requirement") with a target ("one of Nodehour's services"), which is enough to distinguish it from the read-only siblings describe_proposition and list_propositions. It stops short of explaining what a "requirement" is relative to a "proposition", so the boundary with siblings is only implied.

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?

There is no statement of when to use this versus the sibling tools, nor any preconditions such as whether the slug must correspond to an existing service or when to fall back to "anything-else". The agent must infer the entire usage context from the tool name and schema.

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