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

With annotations present, the description substantially exceeds them: it explains owner-email matching (org member owns project, others become a note and nobody is invited), custom-field behavior (only columns named in customFieldColumns), duplicate-skip semantics that reinforce idempotentHint, dry-run behavior, and the required SharePoint permission on the connected Microsoft account. This is rich behavioral disclosure beyond the annotation flags.

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 purpose, then behavior, then the dry-run and permission notes; every sentence carries information. It is somewhat dense, but nothing is repetitive or 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 6-parameter, nested-schema import tool with no output schema, the description covers idempotency, dry-run, mapping semantics, owner handling, and auth requirements well. The dryRun reference that is not backed by the input schema leaves one calling detail inconsistent, keeping it from a 5.

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. The description does add real meaning for mapping (project field to list column) and customFieldColumns (unmapped columns kept only when named). However, it instructs 'Pass dryRun: true' even though dryRun is absent from the schema and additionalProperties is false, introducing a parameter mismatch that could cause an invalid call.

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 (Import) and resource (SharePoint list used as a project tracker) with scope (one project per row into an Onplana portfolio). This is clearly distinguishable from siblings like list_sharepoint_sites, preview_migration, and add_project_to_portfolio.

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 strong positive guidance: use dryRun to preview columns/mapping/rows without writing, and notes re-runs are safe because previously imported rows are skipped. It does not explicitly name an alternative tool (e.g. preview_migration) or state when not to use it, so it falls short of a 5.

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