Describe a resource

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds valuable behavioral context: output is derived from Productive's own OpenAPI document and includes specific contract elements, plus a warning about write no-ops that goes beyond the annotation.

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 dense but efficient: one sentence enumerates the full contract contents, and a second short sentence delivers a high-impact usage warning. Every phrase contributes meaning, with no filler or repetition of the schema.

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 simple one-parameter read-only introspection tool, the description fully specifies what output the agent should expect and when to call it. The lack of an output schema is compensated by the detailed enumeration of returned contract components.

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 100%, and the schema already documents the single 'resource' parameter with examples. The description adds no additional syntax, validation, or format details for the parameter, so it stays at the baseline where the schema does the heavy lifting.

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 precise verb-object relationship: it provides 'the exact contract for one resource' and enumerates the concrete contents such as filter fields, operators, sort keys, and writable attributes. This clearly distinguishes it from siblings like productive_get, productive_list, and productive_describe_custom_fields.

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 explicitly tells the agent to 'Read this before writing' and contrasts a successful write with 'a 200 that changed nothing,' giving a clear trigger for use. It does not explicitly name alternative tools or when not to use it, but the intended context is unambiguous.

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