arsenkin_profile_catalog

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states 'no provider calls', signaling a safe, side-effect-free catalog operation. This is meaningful beyond the tool name and helps an agent understand it will not trigger external actions or require provider credentials.

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 a single sentence that leads with the action and resource, then adds the key safety qualifier 'no provider calls'. Every word contributes value, and there is no redundant filler.

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 has no parameters and an output schema exists, the description covers the main essentials: what the catalog contains and that it is non-invasive. Slightly more context about when to use it in the broader workflow, such as before prepare or submit, would improve completeness, but it is not essential for correct invocation.

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 tool has zero parameters and the schema is effectively empty, so there are no parameter semantics to explain. The description focuses on what the tool returns rather than inputs, which is appropriate for a no-argument catalog tool.

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 uses a specific verb, 'List', and names the exact resources: 'supported profiles, payload fields and example SEO requests'. The 'no provider calls' clause clearly distinguishes this catalog tool from the operational sibling tools like estimate, submit, and cancel.

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 implies this is an introspection/reference tool to consult before making provider calls, but it does not explicitly say when to use it over siblings or mention any exclusion conditions. An agent has to infer that it should be used for discovery before prepare or submit.

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