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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds operational context by stating that XRef index is required for writer/reader analysis and that a relation graph is used for forms and FKs, which is useful behavioral information beyond the annotations.

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 well-structured with scannable labels ('WHEN', 'Triggers', 'Requires', 'Examples') and is front-loaded with the core purpose. Every sentence contributes meaningful information, including multilingual trigger phrases and two concrete invocation examples, with no 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?

For a tool with no output schema, the description gives a solid picture of what the tool returns by listing result categories: writers, readers, forms, reports, and FK relationships. It could be more explicit about output grouping or behavior when the XRef index is unavailable, but the prerequisites and examples make invocation practical.

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%, so the baseline is 3; all three parameters already have descriptions. The examples 'trace_field_lineage('CustTable','CreditMax')' and the LedgerJournalTrans call provide concrete usage context, but the description adds no substantially new parameter semantics beyond what the schema already provides.

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 opens with a specific verb and resource: 'understand the full data lifecycle of a D365 F&O table field' and then enumerates the exact artifact categories involved (writers, readers, forms, reports, FK tables). This clearly distinguishes it from generic search or reference tools even though no sibling is named.

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 'WHEN' section and trigger phrases ('where is field X set', 'data lineage', 'GDPR field audit') give clear context for when to invoke the tool, and the XRef dependency is stated. It does not explicitly name alternatives or when not to use it, so it stops short of a perfect score.

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