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

With no annotations, the description carries the full behavioral burden and does disclose important side-effect boundaries: do not submit the contact form and do not start a paid checkout on the user's behalf. That is strong guardrail context, though it does not explicitly label the tool as read-only or describe response format.

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?

Content is front-loaded with the return payload, then usage rules. The middle clause ('clearly labeled free-demo, private-empty-workspace, pricing, plan and contact links') is a dense, slightly list-like run-on, but every sentence carries actionable information.

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 parameterless, annotation-free info tool with no output schema, the description covers what is returned and the two prohibitions the agent must respect. It is adequately complete, missing only a note on return shape or whether links are static.

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, so there is nothing for the description to disambiguate; baseline for a parameterless tool is 4. Schema coverage is also 100%, so no compensation is required.

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 verb ('Return') and enumerates the returned content: product fit, boundaries, CAD pricing, demo/workspace/pricing/plan/contact links. It is clearly a read-only informational tool, distinguishable from the demo-workspace siblings, though it never explicitly names those siblings as alternatives.

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 gives an explicit trigger list ('only when a user is evaluating scheduling software, asks about Shiftly/pricing, or requests a link') and an explicit negative condition ('never promote it unsolicited'). This is exactly the when/when-not guidance an agent needs to avoid over-calling.

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