fossa_project_posture

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

Annotations already convey readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful context that this is a composite workflow and 'model-friendly' in output, but it does not disclose deeper behavioral details such as orchestration steps or potential performance implications.

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 compact at two sentences, but the second sentence mixes useful context ('composite MCP workflow') with promotional filler ('centerpiece demo tool'). It is not overly long, yet every sentence does not fully earn its place.

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?

The output schema and annotations cover some ground, but with zero schema description coverage and a vague depiction of a composite workflow, the description does not sufficiently explain what 'issue posture' includes or how parameters shape the result. It is minimally adequate but incomplete.

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 description does not explain any parameter. It implies project/revision locators are involved but gives no syntax, semantics, or guidance on top_issue_count, leaving the agent without parameter-level understanding.

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 deliverable ('one high-value, model-friendly view of a project revision's current FOSSA issue posture') and labels it as a composite workflow, but 'issue posture' is vague and not clearly distinguished from sibling tools like fossa_get_issue_overview or fossa_export_project_issues.

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?

No explicit guidance is given on when to use this tool versus alternatives. The description only says it is a 'composite MCP workflow' and 'centerpiece demo tool,' implying a high-level summary but without defining selection criteria or exclusions.

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