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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile does not need restating. The description adds its own behavioural context not in the annotations: results are filtered to the caller's own membership and the ERP enforces that scoping, which tells an agent the result set is permission-bound. It stops short of describing result shape or pagination behaviour.

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 short sentences, with the resource and scope stated first. There is mild redundancy between the phrase "the caller can see" and the sentence "Scoped by the ERP to the caller's own membership," which restates the same permission boundary.

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 zero-parameter, read-only list tool with full annotation coverage and no output schema, the definition covers identity, scope, and downstream use. The only missing detail an agent might want is whether the result set is paginated or bounded, but that is minor at this complexity.

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?

The tool takes zero parameters, which is the baseline-4 case. The description correctly signals that no filtering arguments are needed, since scoping is applied implicitly by the ERP.

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 (list projects) plus a scope qualifier: only projects "the caller can see in their company." The mention of ids "to create assignments against" also hints at how it differs from a create tool or a generic project listing, though it does not name a sibling such as seo_list_projects or erp_create_project.

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?

Uses the pattern "the projects ... with ids to create assignments against," which implies the calling context (fetch ids before erp_create_assignment). However, it never states when not to use this tool or how it relates to any alternative listing tool, so the routing guidance stays inferential rather than explicit.

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