sc_transaction

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

No annotations are provided, so the description bears full behavioral disclosure. It only states 'Get details' without describing auth needs, error behavior (e.g., missing transaction), or what the returned details include. Despite the presence of an output schema, the description adds no behavioral context.

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, concise sentence front-loading the key purpose. However, it is under-specified for the tool's complexity; brevity here sacrifices necessary detail for other dimensions.

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 two parameters and an existing output schema, the description is incomplete. It omits parameter explanations, usage context relative to sc_transactions, and any reference to the output schema. The tool's behavior and prerequisites are not fully clarified.

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 parameters. It fails to clarify the purpose of portfolio_id (optional, nullable) or the format/meaning of transaction_id. With zero schema coverage, the description should compensate but provides no parameter semantics.

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 clearly states the tool retrieves details for a single Scalable Capital broker transaction by ID. It uses a specific verb ('Get details') and resource ('single transaction'), distinguishing it from the sibling tool sc_transactions which likely lists multiple transactions.

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 usage when a transaction ID is available. However, it does not provide explicit guidance on when not to use this tool (e.g., when a transaction ID is unknown) or mention alternatives like sc_transactions for listing transactions first.

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