get_solution_import_log

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

Beyond the readOnly annotation, it discloses important behavior: 2 MiB XML bounds, no DTD/entities/namespaces/execution, raw XML is never returned, failures and warnings are prioritized, error text is opt-in and redacted, and missing/forbidden/unsupported data is distinct from success.

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 front-loaded: it starts with what the tool does, then adds limits, return semantics, redaction behavior, and caveats. Every sentence contributes useful selection or safety context without 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?

Although there is no output schema, the description covers the important return semantics: bounded summaries, manifest/section counts rather than unique components, prioritized failures/warnings, no raw XML, and optional bounded error text. It also explains the success distinctions an agent needs before calling this complex read-only tool.

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 coverage is 71%, and the description adds meaningful semantics beyond it: the job is identified by GUID, result summaries are bounded, and error text is opt-in and bounded with redaction. It still leaves some parameter details, such as top default and max text limits, to the schema.

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?

It states a specific verb and resource: read a native solution importjob data XML by GUID and return bounded result summaries. It also separates itself from status/deployment checks by noting that logs do not prove async completion or deployment, and from record-data importlogs by naming the importjobs source.

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 gives clear context and exclusions, especially that this should not be treated as proof of async completion or deployment success. However, it does not explicitly name the alternative sibling tools to use for status or verification, leaving that routing to inference.

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