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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals only that the observation is attributed and that accepted work is a prerequisite for certain outcomes, but it does not explain side effects, idempotency behavior, validation rules, permission requirements, or what happens on conflict. For a mutation tool with a nested schema, this is insufficient.

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 very short and front-loads the core purpose in the first sentence. The second sentence adds a relevant constraint but is cryptic and could be more explicit. Still, there is no fluff and the structure is reasonably efficient.

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's complexity (nested object, required idempotencyKey, no output schema, no annotations), the description is not complete enough. It says almost nothing about valid values, return behavior, or how the components of the observation object relate to the stated provenance. An agent would have to guess at critical details.

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%, and the description does not explain any of the three parameters or the nested observation properties. The phrases 'attributed' and 'with provenance' vaguely suggest metadata like origin or submissionId, but the agent cannot infer the meaning of idempotencyKey, evidenceNote, kind, blinding, or the UUID fields. The description fails to compensate for the total lack of schema descriptions.

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 first sentence 'Record an attributed observation with provenance' states a specific verb and resource, and the qualifiers 'attributed' and 'provenance' distinguish this from sibling tools like record_history or create_interaction. The purpose is immediately clear and specific enough for an agent to identify the tool's role.

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 contains only a cryptic policy statement 'Qualified and paid-work outcomes require actual accepted work' and does not explicitly say when to use this tool versus alternatives. There is no mention of conditions, exclusions, or sibling comparisons, so the agent receives little guidance on choosing this tool among the many related ones.

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