get_project_workflow_profile

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

With no annotations, the description does disclose an important behavioral trait: it is non-mutating for both Plane and local profile files. However, it does not clarify what 'merged' means (which layers are combined), what happens when project_id is omitted, or any auth/error behavior, leaving meaningful gaps for a tool with zero annotation coverage.

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?

It is a single, front-loaded sentence with zero waste. It could be slightly more useful without becoming verbose, but the structure is efficient and clear.

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?

An output schema exists, so return values need not be explained. Still, the missing usage guidance and the unexplained project_id parameter leave the definition only minimally viable for an agent deciding when and how to call it.

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 single parameter project_id is undocumented in both schema and description. The description never mentions project_id, its nullable default, or whether omission falls back to the active project, so it fails to compensate for the schema gap.

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 states a specific verb and resource: 'Read the merged workflow profile for a Plane project.' The word 'merged' helps distinguish it from simpler context lookups like get_project_workflow_context, but no sibling is named explicitly, so differentiation is only implicit.

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?

It does not say when to use this tool versus get_project_workflow_context, get_workflow_options, or get_project_briefing. The only usage hint is the read-only guarantee ('without changing Plane or local profile files'), which implies a safe-read context but gives no positive selection criteria.

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