crpt_call_raw

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=true; the description reinforces this by mapping HTTP verbs to safety classes (GET=read, DELETE=destructive) and disclosing that confirmations are required. That verb-to-safety mapping and the confirmation requirement are genuine context beyond the annotations, though it stops short of specifying auth or rate-limit behavior.

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?

Front-loaded with the core purpose, then a sectioned Args/Returns layout that is easy to scan with zero padded sentences. The leftover '{svc}_call_method' template placeholder is a minor structural wart.

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?

With an output schema present and rich annotations, the description covers the remaining gaps: verb semantics, confirmation behavior, and full parameter meaning. An agent has enough to invoke it correctly; only required-vs-optional parameter status and auth expectations are unaddressed.

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%, so the description must compensate, and it does: all seven parameters are documented (method, path, host, query, body, confirm_write, i_understand_this_modifies_data), including a concrete path example. It does not mark which are required/optional, so it falls just short of full compensation.

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 specific verb (Execute) and resource (ANY endpoint, including ones not in the catalog) with clear scope via '(full API coverage)'. This differentiates it from crpt_call_method, which presumably handles only catalog methods. The differentiation is clear but relies on a templated placeholder sibling name rather than naming crpt_call_method explicitly, keeping it from a 5.

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?

Implies usage through 'even ones not in the catalog', suggesting this is the escape hatch when a method isn't catalogued, but it never explicitly says 'use crpt_call_method for known methods, use this for uncatalogued endpoints'. The reference to '{svc}_call_method' is about shared confirmation rules, not routing guidance. Usage is inferable but not spelled out.

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