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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world scope, so the safety profile is covered. The description adds real value beyond that by disclosing that result completeness is permission-dependent — billing data requires account update rights and contact emails require an execution permission — which an agent cannot infer from annotations. The phrasing 'if you run it' is vague enough to keep this from a 5.

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?

Two sentences, front-loaded with the resource and its returned fields, with no filler. The conditional-permission sentence is dense but earns its place; only 'if you run it' is needlessly opaque.

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 read-only, single-parameter tool with no output schema, the description adequately covers scope, returned content, and permission-dependent visibility. It does not describe absence/error behavior when the code is unknown, a minor gap for a lookup 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 description coverage is 100% and the single parameter is fully documented with examples ('bcp', 'jchsoft'), so the schema does the heavy lifting. The description only restates that lookup is keyed by account code, adding no format or validation detail beyond 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?

The description names a specific verb and resource ('Account workspace details by account code') and enumerates exactly what is returned: attributes, account-level users, permitted projects, and permitted companies. No sibling tool overlaps with account retrieval, so the agent can route to it unambiguously.

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?

Usage is only implied by the single 'account_code' argument; the description never states when to call this versus other tools or what prerequisites exist. The conditional clauses ('only if you may update the account', 'only if you run it') hint at permission-gated behavior but do not guide tool selection.

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